Contents
- What a municipal app can do
- Administrative services: integrate rather than rebuild
- Native app, web app or both?
- Accessibility and data protection: non-negotiable
- Push notifications with a sense of proportion
- Plan procurement, operations and editorial work
- Costs of a municipal app
- Conclusion
- Frequently Asked Questions
A municipal app brings a town’s or city’s services to where residents already are every day: their smartphone. Reporting issues, checking waste collection dates, booking appointments at the citizens’ office or receiving alerts – done well, the app relieves the administration and makes services visible. This article helps municipalities, public utilities and municipal IT providers plan such a project realistically, using the German public sector as the reference point.
What a municipal app can do
Most municipalities have a website, and many offer online services via state or federal portals. An app adds value when it offers features people need regularly and that benefit from smartphone capabilities:
| Service | Added value of the app | Effort |
|---|---|---|
| Issue reporting | Photo and location straight from the pothole or broken street light | Medium |
| Waste collection calendar | Push reminder the evening before, street saved once | Low |
| Citizens’ office appointments | See free slots, book and cancel | Medium, depends on the scheduling system |
| News and alerts | Roadworks, closures, severe weather, events | Low to medium |
| Events calendar | Clubs, culture and markets in one place | Low |
| Links to online applications | Direct entry into existing administrative services | Low |
| Participation | Surveys, participatory budgets, idea submissions | Medium |
| Parking, pools, library | Availability, tickets, membership cards | High, depending on third-party systems |
The most important success factor is a core feature that brings people back regularly. Waste calendars and issue reporting are exactly such anchors in many municipalities.
Administrative services: integrate rather than rebuild
In Germany, formal administrative services such as applications, certificates and registrations are being digitised under the Online Access Act (OZG) through existing portals and specialist systems. A municipal app should generally not rebuild these services but integrate them sensibly: via links, embedded web views or – where interfaces exist – deeper integration. For identification, central user accounts such as BundID and the online function of the national ID card are available.
This division of labour saves budget and avoids duplicate maintenance. The app becomes a friendly entry point, while legally binding processes run in the systems designed for them.
Native app, web app or both?
For municipalities, the platform question is also a budget question. A progressive web app is reachable without an app store, runs on all devices and can be tied closely to the website. Native or cross-platform apps score with push notifications, camera and location integration and visibility in the stores. A detailed comparison is in our article on the progressive web app.
In practice, a cross-platform app built with React Native or Flutter that pulls content from the website’s existing CMS often works well. That way the press office maintains news only once.
Accessibility and data protection: non-negotiable
Public bodies in the EU are required to make their websites and mobile apps accessible; in Germany this is governed by the Disability Equality Act with the BITV 2.0 ordinance and corresponding state laws. This covers sufficient contrast, scalable text, screen reader support, plain language and an accessibility statement. How to implement this technically is described in our article on accessible apps.
On data protection, residents expect particular care from their local authority. In concrete terms:
- Use without registration for all information services.
- No third-party tracking or advertising SDKs; statistics only in a data-minimising way and with consent where required.
- Location access only for issue reporting and only at the moment of reporting.
- For report photos, warn about identifiable people and number plates or blur them.
- Hosting in Germany, ideally in municipal or certified data centres.
Agree the exact requirements with your data protection officer; this article is not legal advice.
Push notifications with a sense of proportion
Push is a powerful tool for municipal apps – and easily overused. A topic subscription model has proven its worth: users choose whether they want to hear about waste collection, road closures, events or only urgent warnings. District-level notifications increase relevance further. Important: official hazard warnings have established warning systems; a municipal app should complement them, not replace them. More tips in our article on push notifications.
Plan procurement, operations and editorial work
Public clients have to follow procurement law. A precise specification covering features, accessibility requirements, hosting rules, operation and maintenance services, and arrangements for source code and usage rights makes offers comparable. Pay particular attention to:
- Source code ownership: whoever holds the rights to the code can switch providers later or share the app with other municipalities.
- Operations and updates: operating system updates require regular adjustments – this belongs in the maintenance contract.
- Editorial responsibility: who maintains news and events, who handles issue reports and within what time frame?
- Interfaces: waste management, appointment system, CMS and the departments’ ticketing systems.
- Metrics: active users, number and handling time of reports, push subscriptions.
Costs of a municipal app
| Scope | Example | Guide price |
|---|---|---|
| MVP | Waste calendar, news from the CMS, topic-based push | €5,000–15,000 (4–8 weeks) |
| Mid complexity | Plus issue reporting with back-office view, appointment booking, events, iOS & Android | €15,000–50,000 (2–4 months) |
| Platform | Several municipalities or utilities, citizen account, payments, many specialist systems | from €50,000 (from 4 months) |
AI-assisted development can cut cost and time by up to 40 %. Smaller municipalities in particular should also consider developing an app together with neighbouring towns or the district. You can request a non-binding fixed-price offer through our offer wizard.
Agentic coding workshop for your team? From €799 net – request a quote by e-mailConclusion
A municipal app convinces when it does a few things very well: reliable everyday information, simple reporting to the administration and a friendly entry into digital government services. Accessibility, data protection and clear editorial responsibilities are not extras but the foundation of trust. Settle source code rights and maintenance properly as well, and you stay in control in the long term.
Frequently Asked Questions
How much does a municipal app cost?
As a guide, a starter version with waste calendar, news and push costs €5,000–15,000. With issue reporting, appointment booking and events for iOS and Android, budget typically €15,000–50,000.
Does a municipal app have to be accessible?
Yes, public bodies are required to make their mobile apps accessible as well and to provide an accessibility statement. The details follow from national and, in Germany, state law.
Should the app handle administrative applications itself?
Usually not. It makes more sense to integrate existing online government services and user accounts such as BundID rather than developing legally binding processes twice.
Can several municipalities share one app?
Yes, a multi-tenant app with shared features and separate content per municipality lowers the cost per authority. It requires clear arrangements on rights, operations and editorial work.