What App Maintenance Actually Involves After Launch
- Mobile
- Maintenance
- Business
Launch is the beginning of an app’s life, not the end of its costs. This is what keeps it working, and what happens when nobody does it.
An app that is not maintained does not stay the same; it decays. The phone it runs on changes every year, the stores change their rules, the services it depends on change their APIs. Planning for this from the start is cheaper than discovering it when the app stops working.
The yearly OS releases
Apple and Google ship a major iOS and Android version every year. Each one deprecates APIs, tightens permissions and changes how background work, notifications and privacy prompts behave. Most apps need at least some changes to keep working properly, and the stores eventually require builds made with recent tools.
Store policy changes
App Store and Google Play rules move continuously: privacy declarations, account deletion requirements, target API levels, payment rules. An app that was compliant at launch can be blocked from updating, or removed, until it catches up. This work is rarely large, but it arrives on someone else's schedule.
Dependencies and SDKs
Every app is built on libraries and third-party SDKs: analytics, payments, maps, crash reporting. They release security fixes, deprecate old versions and occasionally shut down. Keeping them reasonably current is far easier in small, regular steps than in one painful upgrade two years later.
Watching the app in production
Crash reporting and performance monitoring tell you what users experience on devices you never tested. Someone needs to read them, spot the crash that affects one phone model or one OS version, and ship the fix. Without that, the first sign of a problem is a one-star review.
The backend and the bills
Most apps have a server side: an API, a database, file storage, push notifications. Servers need security updates and backups, certificates and domains need renewing, and usage-based costs need watching as the user base grows. This is part of maintenance even though it is invisible in the app itself.
Small improvements
Bug reports, support questions and reviews point to small fixes that make a real difference to retention. Maintenance that only keeps the app alive, without ever improving it, tends to lose users slowly.
Planning for it
- Ask for maintenance to be described before the build starts, not after launch: what is covered, how quickly issues are handled, and how changes are requested.
- Make sure you own the accounts: the developer accounts, the repository, the cloud services. Maintenance is impossible without them.
- Budget for it as a running cost, alongside hosting and the store fees, not as an occasional emergency.
We maintain our own apps on the App Store through every one of these changes, which is why we talk about maintenance at the start of a project rather than the end. Our notes on release pipelines and store rejections cover two parts of it in more depth, and our mobile service describes how we work.