Launch is the start of an app's life, not the end of the project. Plan the budget and the contract for ongoing work at the same time as the build, so updates don't turn into emergencies.
What drives maintenance work
- Yearly OS releases. Apple and Google release major iOS and Android versions every year. New versions can change permissions, background behaviour and interface details, so test against the betas before release.
- Store requirements. Google Play requires apps to target a recent Android API level by set deadlines, or updates can be blocked and the app can become harder to find for users on newer devices. Apple periodically requires builds made with recent versions of its tools.
- Dependencies. Frameworks, plugins and SDKs release updates and security fixes and sometimes stop supporting older versions.
- Expiring credentials. Signing certificates, some push notification credentials and API keys expire or rotate and must be renewed before they lapse.
- Your backend and integrations. If a connected service changes its API, the app has to change too.
- Real-world bugs. Crash reports from devices and OS versions nobody tested.
How support is usually arranged
| Arrangement | How it works | Suits |
|---|---|---|
| Monthly retainer | A set block of hours each month for updates, fixes and small features | Apps with steady use and regular change |
| Maintenance-only plan | OS compatibility, dependency and store-requirement updates, critical fixes | Stable apps with few new features planned |
| On request | Work estimated and billed per job | Simple internal apps, low change |
Define support terms in writing
- What counts as a critical issue, and how quickly someone starts on it.
- What's included (OS updates, dependency upgrades, monitoring) and what's quoted separately (new features).
- Whether unused hours roll over.
- Who monitors crash reports and store emails, and who renews certificates.
- How the arrangement ends and what is handed over if it does.
Monitoring
Crash reporting and basic usage analytics tell you what's breaking and which features people actually use. Remember that any SDK you add must be reflected in your store privacy disclosures. Keep monitoring to what you'll act on.
What affects maintenance cost
The number of platforms and codebases, how many third-party SDKs the app depends on, the size of the backend, how often you want new features, and how up to date the app was kept before. An app left untouched for several years usually needs a larger catch-up effort before new work can start.
Already have an app that needs updates? Describe it in your brief, including who built it and what access you have.
Send a project brief