Key takeaways
- An app stops being updatable if nobody maintains it: Apple and Google set dates after which apps must be built with newer tools.
- Separate support (fixing what breaks), maintenance (planned updates) and enhancements (new work) in any contract you sign.
- A good maintenance contract names the work covered, response times by severity, the hours included and what is left out.
- There is no fixed rule for the yearly cost. Estimate it from what the app depends on, and keep hosting and other running costs as separate lines.
- Plan at least one round of platform updates a year, before the store deadlines rather than after a rejection.
An app that was built, tested and approved can feel finished, so the bill that keeps arriving after launch can look like padding. It isn’t, because the phones, the app stores and the services the app connects to keep changing around it, and some of those changes come with deadlines. What follows covers what breaks when nobody maintains an app, with the store rules that are in force now, what each level of maintenance contract should include, how to estimate the yearly cost, and a sample calendar for the year.
What does app maintenance cover?
App maintenance covers the planned work that keeps a live app working: updates for new operating systems and store rules, security patches, package upgrades, fixes when an outside service changes, and the monitoring that spots problems before users do. Three words get mixed up in quotes, so separate them:
- Support is reactive: answering bug reports and user problems, and fixing what is broken.
- Maintenance is planned: the updates and checks that stop things breaking, done on a schedule whether or not anything has gone wrong.
- Enhancements are new work: new features, new screens and changes to how the app behaves. They are usually priced separately, or covered by a set number of hours a month.
A maintenance contract can include all three, but they should be named separately, with what each one covers. A contract that says only “maintenance and support” leaves you to find out what that means on the day you need it.
What breaks if nobody maintains the app?
Store submissions break first: Apple and Google both set dates after which apps must be built with newer tools, and an app that misses them can’t be updated, or, on Google Play, stops reaching new users on newer phones. Security and outside services follow. The rules below were checked on Apple’s and Google’s own pages on 20 October 2026.
These are not one-off events. Apple and Google have raised their minimums year after year: Apple’s upcoming requirements page lists SDK minimums for 2023, 2024 and 2026, and Google’s target API level requirements set a new minimum for 2026, above the one existing apps must already meet. Plan for one round of platform updates a year at the least, before the deadlines rather than after a rejection.
App needs looking after?
Tell us what your app runs on and when it was last updated, and we’ll talk through what keeping it current involves.
What should an AMC include?
An AMC should list exactly what work is covered, how fast problems are answered, how many hours of small changes are included and what you get back each month, such as a short report. For an app, three levels cover most needs; what changes between them is how much is done before a problem appears.
Whichever level you choose, ask for these in writing:
- Response times by severity: how quickly the team answers and starts on an outage, a broken feature and a minor issue, and whether that applies at weekends.
- The hours included, what happens to unused hours, and the rate for work beyond them.
- What counts as a bug (the app not doing what was agreed) and what counts as a change (doing something new). That one definition settles most arguments.
- Who holds the accounts: the code repository, the store listings and the hosting should sit in your company’s name, with the maintenance team given access.
- How you leave: how much warning either side gives to end the contract, and what is handed over when it ends.
What is left out of an AMC?
Running costs, new features and problems caused by changes someone else made are usually outside an AMC, so check the exclusions as carefully as the inclusions. The common ones:
- Running costs, paid to the providers, directly or passed on at cost: hosting, the Apple Developer Program at USD 99 a membership year, which may vary by region (shown in local currency at sign-up) (Apple) and Google Play’s USD 25 one-time registration fee (Google Play Console Help), both checked 20 October 2026, plus messaging, maps, email and AI usage.
- New features and redesigns, beyond any hours the contract includes.
- Fixes after someone else changes the code, such as your own developers or another vendor.
- Content and data work: updating text, prices or images in the app, unless the contract names it.
- Tax: in India, check whether the quoted price includes GST.
How much does app maintenance cost a year?
There is no fixed industry rule for the yearly cost: the honest answer is to estimate it from what the app depends on and how much you plan to change it. For our own planning we use 15–20% of the build cost a year *, with the hosting, store fees and outside services on top, each billed at cost. Our app development cost guide shows that figure next to the build ranges.
A percentage is a starting point, not an estimate. Two apps that cost the same to build can need very different maintenance, depending on the factors below.
To turn this into a number, ask the team for an estimate in hours: the platform updates for the year, a monthly allowance for patches and fixes, and the small changes you expect. Then add the running costs line by line. Our monthly Care and Growth plan adds small changes and an analytics review on top of basic upkeep; the ranges are on our pricing page.
What does a year of maintenance look like?
A year of maintenance is a monthly routine of monitoring and patches, plus a few fixed points set by the store deadlines and your own plans. The calendar below is a sample for an app on both stores; the store dates are 2026’s, so check Apple’s and Google’s pages for the next year’s.
Every month
Check crash reports, uptime and store reviews. Apply security patches and package updates. Renew anything close to expiry.
January to March
Plan the year: read Apple’s and Google’s requirement pages, list each integration’s upcoming changes, and set the year’s update windows.
April to June
Apple’s yearly build rules: in 2026, Xcode 26 and the iOS 26 SDK applied from 28 April. Update, test and submit before the date.
July to September
Google’s yearly target: in 2026, Android 16 (API level 36) and Billing Library 8 applied from 31 August. Update and submit before the date.
October to December
Review the year: test on the newest iOS and Android, check security and access, and agree next year’s scope and budget.
A sample calendar for an app on both stores. The store dates are 2026’s; next year’s are set by Apple and Google, so check their pages each January. Checked 20 October 2026.
Keep the calendar where both sides can see it, and put the next store deadline in it as soon as Apple or Google publishes it. The cost of a platform update depends a lot on how many outside packages the app uses; our guide to Flutter or React Native covers what drives the upkeep of each.
How do you choose who maintains your app?
Choose the team that can show you how it would run your app’s maintenance: what it would check each month, which deadlines are coming, and how it would report back. Ask it to look at your code before quoting, so the price is based on the app you have, not a guess.
Our own maintenance work includes Crime and Punishment for the Vidhi Centre for Legal Policy, a database of 7,305 crimes across 370 central laws that Tailwebs built and maintains. If you have an app that needs looking after, or one that hasn’t been updated for a while, see our mobile app development page or our pricing for the monthly plans.
