
Klimaticket Tracker
In Brief
- Type: Flutter App
- Period: 2022 – present
- Downloads (April 2025):
- Android: ~ 1,700
- iOS: ~ 7,500
- Total: ~ 9,200
- Monetization: Donations
Links
The Problem
In 2021, Austria introduced the Klimaticket. This is an annual pass for public transport that includes all means of transportation throughout Austria. In addition to a nationwide ticket, there were also various tickets for each federal state and different regions.
Like many others, I purchased a Klimaticket and wondered whether the purchase would be worthwhile.
The Solution

Instead of tracking all travel costs in an Excel file or keeping a written record, I decided to develop a small app that could answer this question.
The requirements were relatively simple. Users can select their Klimaticket in the app (or enter its price) and continuously record their journeys and their costs.
The app then shows users various information about their travel behavior and their Klimaticket:
- Days in use: How long has the Klimaticket been in use?
- Proportional price: How much has the Klimaticket cost so far in relation to the duration of use?
- Sum of journey costs: How much would it have cost to pay for all journeys individually?
- Balance: If the sum of journey costs is greater than the proportional price, the Klimaticket has been worth it at this point.
- Progress: What percentage of the Klimaticket price would I have already spent on journey costs?
Additionally, the app includes several features that simplify expense tracking:
- Templates for expenses
- Categories
- Statistics
The Klimaticket Tracker app is available free of charge. However, users can support the project through donations.
Technical Details
This project gave me the opportunity to return to my proven app architecture built around the state management solution Riverpod.
Unlike the Trexpense Project, where I used Sembast as the database solution, for this project I used Hive.
The project is hosted on GitHub, and fastlane is used for deployment.
I designed the UI myself, closely following the Material Design guidelines.
The 3 Most Important Lessons for Future Projects
1. It’s Worth Publishing Even Small Projects
Since I originally developed the app only for my own use, I was positively surprised by the demand. Even without advertising, the app has been downloaded by over 9,000 users so far.
2. Not Every Requested Feature Makes Sense
Over time, I repeatedly received requests for new features. It was important not to say yes to everything. My question was always: Will it benefit the majority of users?
3. Apple Doesn’t Allow Donation Links
For users who wanted to support the project, I integrated a donation link. The app was subsequently rejected from the App Store. All payments (whether voluntary donations or not) must be processed through Apple (which retains 15–30 % of the amount).