Topic Mobile and app development

App Maintenance After Launch: What It Covers and Costs

The short answer

App maintenance is the regular work that keeps a live app running, secure and accepted by the app stores: operating system and store updates, security patches, fixes to outside services, monitoring and small changes. Plan for it from launch, under an annual maintenance contract (AMC) or a monthly plan, because an app nobody updates soon stops being updatable.

Written by

Siddharth Kajaria, Founder and CEO

Published

Reading time

11 min read

A wall clock with its glass cover swung open as a hand winds it with a key, an oil can on the shelf below.
In this post11 min read
  1. What does app maintenance cover?
  2. What breaks if nobody maintains the app?
  3. What should an AMC include?
  4. What is left out of an AMC?
  5. How much does app maintenance cost a year?
  6. What does a year of maintenance look like?
  7. How do you choose who maintains your app?

Key takeaways

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.

9 things that break

Store rules checked 20 October 2026

Apple’s rules

  1. Newer Xcode and SDK for every upload

    What to do
    Upgrade the build tools and the framework, then retest on current iPhones and iPads.
    If nobody does it
    The next update, even a one-line fix, can’t be uploaded until the app is rebuilt.
  2. A minimum iOS version to support

    What to do
    Check the oldest iOS version the app supports and raise it where it must go up.
    If nobody does it
    An old configuration blocks the upload, and old code paths go untested.
  3. Reasons for sensitive system calls

    What to do
    Keep packages current, so their own declarations are included, and add the app’s own.
    If nobody does it
    An upload is refused because an old package never added its declaration.

Google’s rules

  1. A newer target Android version

    What to do
    Raise the target version each year and test the behaviour changes that come with it.
    If nobody does it
    Updates can’t be submitted, and an app below Android 15 (API level 35) is no longer offered to new users on newer phones.
  2. Google Play Billing Library

    What to do
    Upgrade the billing package, and test purchases and subscriptions end to end.
    If nobody does it
    Play Console flags the app, and updates must be upgraded, or get an extension, to be accepted.
  3. New Android versions on users’ phones

    What to do
    Test the app on the newest Android version as soon as it is available.
    If nobody does it
    Features such as notifications or location quietly stop working for users on new phones.

Security and outside services

  1. Security patches in packages

    What to do
    Check for security releases every month and apply them, starting with the most serious.
    If nobody does it
    A known flaw stays open in the app or its server, where anyone can look it up.
  2. Outside services that change

    What to do
    Watch each provider’s announcements and plan the upgrade before the old version is switched off.
    If nobody does it
    Payments, sign-in or messages fail on the day the old version is turned off.
  3. Certificates and push notifications

    What to do
    Keep a list of every certificate and key with its expiry date, and renew in good time.
    If nobody does it
    Push notifications or secure connections stop working until someone finds out why.

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?

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.

Generic levels, not our plans

Three levels of app maintenance contract and what each should include
Should includeBasicKeep it runningStandardKeep it currentGrowthKeep it improving
Platform and store updatesThe yearly updates the stores require, done before the deadlinesThe same, plus testing on each new iOS and Android version as it shipsThe same, plus adopting new platform features where they help users
SecuritySerious security fixes applied as they are publishedMonthly patching of packages and serversMonthly patching, plus a yearly review of security and access
Bug fixesFixes for anything that stops the app workingFixes for all bugs against what was agreedAll bug fixes, ranked with you each month
MonitoringCrash reports and uptime alertsCrash reports, uptime, error rates and store reviewsAll of that, plus a monthly look at usage and analytics
Small changesNone, or charged by the hourA few hours a monthA set block of hours each month for improvements
Response timesBusiness hours, for outagesAgreed by severity, with outages firstAgreed by severity, with cover outside business hours if you need it
ReportingA short note when work is doneA monthly report of what was done and what is comingA monthly review call with the next month’s plan
Best whenThe app is stable, changes rarely and has few users or integrationsThe app is in daily use by customers or staff and has to keep workingThe app is the product, and you plan to keep improving it after launch

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.

What moves the yearly cost of maintaining an app, and how to estimate each part
What moves itWhy it adds hoursHow to estimate it
PlatformsEach store and each platform has its own yearly update, test pass and submission. A web admin panel adds its own.Count the apps and panels, and allow one update round a year for each.
Outside packagesEvery package has to keep up with the framework and the stores. An abandoned one has to be replaced.Ask for the list of packages the app uses, and how many are out of date today.
IntegrationsEach payment, messaging, maps or company system can change its API or rules, on its own timetable.List each integration and check its provider’s retirement dates for old versions.
How much is riding on itAn app that takes payments or runs operations needs faster responses and closer monitoring than a brochure app.Decide the response time you need for an outage, and price the level that gives it.
How often you change itSmall changes every month need a block of hours; an app you leave alone needs only the updates.List the changes you expect in the next year and estimate them separately from upkeep.
The state of the codeCode without tests or documentation takes longer to change safely, and every update has to be checked by hand.Ask for a short code review before agreeing the monthly scope.

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.

  1. Every month

    Check crash reports, uptime and store reviews. Apply security patches and package updates. Renew anything close to expiry.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

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.

02 FAQ

Questions, answered

Can I skip maintenance for a year and catch up later?
You can, but catching up usually costs more than keeping up. A year of skipped updates means several framework and package versions to jump at once, a store deadline that may already have passed, and security fixes applied late. Catching up becomes a project with its own testing, rather than a routine monthly task.
Can a different team maintain the app from the one that built it?
Yes, if the code, the documentation and the accounts are handed over properly. Expect the new team to spend the first weeks reading the code and setting up builds before they work at full speed. Ask for a short audit first, so you know the state of the code before you agree a monthly scope.
Is hosting part of app maintenance?
Usually not. Hosting, store fees, messaging, maps and AI usage are running costs, billed by the providers, and they grow with your users. Maintenance is the engineering time to keep the app working. Keep the two as separate lines in your budget, so a jump in one does not hide in the other.
What is the difference between support and maintenance?
Support answers when something goes wrong or someone has a question: a bug report, a user who can't sign in, a failed payment. Maintenance is the planned work that stops things going wrong: updates, patches and checks. Most contracts include both, so check how much of each you are paying for and how fast support responds.
Have business queries?
Chat with us