A Smart City app where a resident settles a matter instead of calling the town hall
We build city apps for municipalities and public utilities. Just as often we take over an app written by another contractor and move it forward module by module, without a rewrite from scratch. One codebase for iOS and Android.
Problems we solve
Problem: A resident who wants to report a streetlight that has come down or a pothole first has to work out which department handles it, then call during office hours.
Solution: The resident files a report on their phone in 5 steps: category, description, a point on the map, photos and a preview before sending. It goes straight to the department responsible for that category, and the resident can follow its status.
Problem: News about a water outage or a diverted bus route goes out on the website and social media, so it reaches only some residents, and usually too late.
Solution: Alerts arrive straight to the phone, split by category and by the institution that issued them. Residents choose which categories they subscribe to, while safety messages go to everyone who has the app, whatever their settings.
Problem: The waste collection calendar sits on the website as a PDF, and residents still forget to put the bin out.
Solution: The same dates, but tied to a specific address, with a reminder at a time the resident picks and each collection written into the phone calendar. There is also a map of bulky-waste drop-off points.
Problem: Drivers do not know whether they are in a paid zone, what it will cost or which operator handles it, so they park and hope for the best.
Solution: Zone information, a cost calculator and a direct hand-off to the app of one of 6 payment operators. The driver pays in the app they already have installed, and you get the parking module live without a separate payments project.
Problem: The city holds data on timetables, waste and reported issues, but each system stands on its own and residents cannot reach any of them from a phone.
Solution: We connect the app to the systems you already run: the issue reporting register, waste management and timetables, including the GTFS Realtime feed with live vehicle positions. We do not replace your backend; we expose it to the app through an API.
Problem: An app run by a public body has to meet digital accessibility requirements. Added at the end, accessibility comes down to a statement that the first screen reader user proves wrong.
Solution: We build screen reader labels and text size control from day one, and we write the accessibility statement alongside the app rather than before handover.
Problem: The city app was built years ago, the contractor moved on, and the next one is afraid to touch it and proposes rewriting everything from scratch.
Solution: We take over the app from the previous contractor as it stands and modernise it module by module: we split one area into layers, put its error handling in order and release it, while the rest carries on unchanged. A full rewrite costs more, and residents get nothing new while it runs.
Problem: An app released once and then left alone starts to break with each new version of Android and iOS, and by the time even a small fix is needed, everything has to be caught up at once.
Solution: We maintain the app after launch: we update the libraries and the supported system versions, fix the faults residents report and ship new releases to both stores. Changes then arrive in small batches instead of one large operation every few years.
Case study: Smart City Poznań
How we did it in practice
Challenge: The official city app of Poznań has been in the App Store and on Google Play since 2020. An app developed for that long has to keep adding modules and tidying up older ones without ever disappearing from residents' phones.
Solution: We develop the app in Flutter, from one codebase for iOS and Android. We add and modernise one module at a time, so the app stays available to residents the whole time.
Result: Matters that used to mean a phone call to the town hall or hunting for a PDF on the website are now settled from a phone: a fault report with a photo, the waste collection schedule for your address, timetables with live vehicle positions and the paid parking zones.
Features we shipped
Technology
- Flutter
- BLoC and Cubit
- auto_route
- Retrofit + Dio
- injectable + get_it
- Google Maps
- GTFS Realtime (protobuf)
- Firebase Cloud Messaging
- flutter_local_notifications + workmanager
- Sentry and Crashlytics
Delivery time
A first release covering a few modules usually takes 4 to 6 months. When we take over a running app, we can ship the first release of our own within 2 to 3 weeks.
Budget
As a rough guide, a city app built from scratch costs 7,000 to 14,000 EUR net depending on the number of modules and on how many of your existing systems the app has to talk to. For an app that is already live we bill differently, normally on a time-and-materials basis. With somebody else's code that is the fairest arrangement, because nobody can quote up front for something they have not yet seen, and the number of hours a month is agreed as the work goes on. We name the rate once we have discussed the scope. We work out of Kraków, which is why these figures sit below Western European rates. You can price your own scope in the calculator at /en/estimate.
Frequently asked questions
Will you take over an app written by another contractor? +
Yes, and it does not have to be a city app. Taking over a project from another contractor is a large part of our work, across different industries. We start by reading through the code, then agree which modules get rewritten first and ship releases without any gap in availability. After that we stay with the project for support and further development.
Does an existing app have to be rewritten from scratch to be made maintainable again? +
Usually not, because a rewrite from scratch costs more and pushes every new feature further away. We refactor module by module: we take one area, rewrite it into a clear architecture and release it, while the rest of the app carries on unchanged. That way the app stays in the stores and keeps getting new features.
Does a Smart City app need its own backend? +
Not necessarily. Most often we connect to the systems a city already runs, such as the issue reporting register, waste schedules or timetables in the GTFS format. We build a backend only when the data the app collects has nowhere to be stored in the existing infrastructure.
How much does an app for a city or municipality cost? +
Built from scratch it is 7,000 to 14,000 EUR net depending on the number of modules and connections to city systems. Taking over an app that is already live is billed by the hour, on a time-and-materials basis. You can price your own scope at /en/estimate.
Will the app meet digital accessibility requirements? +
Yes. We plan accessibility from the first day of work rather than adding it before handover. Alongside screen reader labels and text size control we prepare an accessibility statement with an address a resident can report a problem to.
Do residents have to create an account to use the app? +
Some features work without an account, among them alerts and city information. An account is required where a case needs a reply, which mainly means reported issues. The account itself is confirmed with an SMS code.
Find out what your app would cost
In a few seconds you get a rough cost and delivery time for your app.
Go to the estimate calculator