An app is not finished when it reaches the store. Android and iOS change every year, libraries go out of date and users find issues. Here is what maintenance involves, what it costs and how to budget for it.
What maintenance covers
- Store requirements. Google Play raises its minimum target API level every year, and both stores update their policies. See the Google Play target API requirement.
- Library and SDK updates. Login, payments, maps and analytics libraries all release new versions, and old ones stop working.
- Bug fixes. Real users on real devices find problems that testing missed.
- Small improvements. Feedback turns into small features and changes.
- Running costs. Servers, databases or other services the app depends on.
Fixed running costs
| Item | Typical cost |
|---|---|
| Google Play developer account | A one-time fee of US$25 |
| Apple Developer Program | US$99 a year, if you publish on iOS |
| Backend, database or server | From a small monthly fee, growing with your users |
| Domain for a website or API | A small yearly fee |
Budgeting for the work
A common rule of thumb is to set aside a part of the original build cost each year for maintenance. The real figure depends on how much the app does and how often you want to improve it. A simple way to plan:
- One planned update a year for target API and library upgrades.
- A small budget for fixes that come up between releases.
- Improvements when you need them, scoped as small fixed jobs.
Planning once a year is almost always cheaper than waiting until an urgent fix is blocked by an outdated app.
What we charge
We price maintenance per job, so you only pay for work that is needed. A target API update or a few focused fixes is typically £300 to £950 and takes 2 to 5 days. Larger dependency upgrades are typically £700 to £1,700. Small improvements to an existing app are typically £650 to £1,700.
We also take on apps built by someone else. We start with a short code review and agree the work in writing. See app maintenance for the details.