App maintenance: what it involves and what it costs

Budget 15 to 25 percent of the build cost a year, plus hosting and services. What app maintenance covers, the yearly store deadlines and what to skip.

By Sohail Hussain21 November 20266 min read

App maintenance is the work that keeps an app installable, working and allowed in the stores after launch: updating it for each new iOS and Android version, meeting Apple's and Google's yearly SDK and API deadlines, upgrading libraries, keeping the backend secure and running, and fixing bugs. As of October 2026, budget 15 to 25 percent of the original build cost per year for that work, plus backend hosting of roughly US$20 to 300 a month, third-party services of US$30 to 300 a month, and Apple's US$99 yearly developer fee. New features are extra.

An app with no maintenance budget does not fail on day one. It fails quietly, over twelve to eighteen months, as new phones and new store rules move away from it.

What does app maintenance actually involve?

Six kinds of work, most of which happen whether or not you want new features:

  • OS updates. Apple ships a major iOS version every September, and Google ships major Android versions each year. Each one changes permissions, background behaviour, screen layouts or deprecated APIs, and some part of most apps needs adjusting.
  • Store requirements. Both stores set minimum build requirements every year (below), and change policies on privacy, data safety, account deletion and age ratings more often than that.
  • Framework and library upgrades. React Native, Expo or Flutter, plus every library for payments, maps, analytics and notifications. Falling more than a version or two behind turns a day's upgrade into weeks.
  • Backend and security. Server updates, database backups, dependency security patches, expiring certificates and keys, and monitoring that someone actually reads.
  • Bug fixes. From crash reports and user reviews, prioritised by how many people they affect.
  • Small changes. Text, prices, a new field on a form. Not features, but not nothing.

This is the work our mobile app development service plans for from the first estimate, because an app quote without a maintenance line is a quote for a build, not for an app.

Which yearly deadlines can you not skip?

DeadlineWhen, as of October 2026What happens if you miss it
Apple minimum SDK for uploadsEach spring; since April 28, 2026, builds must use Xcode 26 and the iOS 26 SDKYou cannot upload any update, including an urgent fix
Google Play target API levelEach August 31; in 2026, Android 16 (API 36) for new apps and updatesYou cannot publish updates; apps too far behind are hidden from new users on newer phones
New iOS releaseEach SeptemberWhatever the new version breaks stays broken for your users
New Android releaseEach year, now usually mid-yearAs above, on Android
Apple Developer Program renewalYearlyThe app is removed from sale until you renew
Signing and push certificatesApple distribution and push certificates last a year; token-based push keys do not expireBuilds or push notifications stop working until renewed
Store declarationsWhenever policies changeWarnings, then blocked updates or removal

Apple publishes its build deadlines on the upcoming requirements page, and Google publishes its schedule in the target API level requirements. Put both in the company calendar with a reminder two months before.

How much does app maintenance cost?

For an app that cost US$60,000 to build, the first year after launch typically looks like this, as of October 2026:

ItemMonthlyYearly
Maintenance work: updates, upgrades, fixes (15 to 25 percent of build)US$750 to 1,250US$9,000 to 15,000
Backend hosting at low to moderate usageUS$20 to 300US$240 to 3,600
Services: push, crash reporting, analytics, email, SMSUS$30 to 300US$360 to 3,600
Apple Developer ProgramUS$99
Google PlayOne-off US$25 at sign-up

These match the ranges in how much a mobile app costs. The low end is a stable app with few integrations and a small user base. The high end is an app with payments, several third-party services, a busy backend and users who report every bug. SMS for phone-number login is the line that grows fastest with sign-ups.

The first year after launch costs more than later years, because real users find the problems testers did not. Plan for the top of the range in year one.

What happens if you stop maintaining an app?

Not much, at first. That is the trap.

For the first few months, the app keeps working. Then a new iOS version changes something, and a screen misbehaves for users who update. You try to ship a fix and find the build tools are a year out of date: the project will not compile with the Xcode version Apple now requires, and upgrading the framework means upgrading a dozen libraries that changed in the meantime. The one-day fix becomes a three-week upgrade project, charged at short notice.

On Google Play, apps that fall too far behind the target API level stop being shown to new users on newer devices. On the App Store, Apple's App Store Improvements process flags apps that have not been updated in three years and are barely downloaded, gives the developer 90 days to update, then removes them. Apps that crash on launch are removed immediately.

What can you skip or do less often?

Maintenance is necessary; a large monthly retainer often is not. For a small app with stable scope, you can reasonably:

  • Batch updates. A quarterly update cycle, plus the yearly deadlines and urgent fixes, is enough for many business apps. Weekly releases are for products that are still changing fast.
  • Skip cosmetic redesigns. When Apple or Google changes its visual style, you do not need to restyle the app that year unless it looks broken.
  • Raise the minimum OS version. Supporting phones from five years ago multiplies testing. Look at your analytics and drop versions few of your users run.
  • Avoid paying for idle monitoring. Crash reporting and uptime alerts are cheap or free; a retainer that bills for "monitoring" without acting on it is not.

What you should not skip: the yearly SDK and target API updates, security patches on the backend, and reading the crash reports.

How should a maintenance agreement be structured?

Ask for a written agreement that states:

  1. What is included: the yearly OS and store updates, library upgrades, security patches and a number of hours for fixes and small changes.
  2. What is not: new features, redesigns and new integrations, quoted separately.
  3. Response times for a crash affecting many users, compared with a minor bug.
  4. Who owns what: the developer accounts, the code repository, the backend hosting and the domain, all in your company's name. The same rules apply as for a website; see website maintenance for the web side.

Our app cost calculator gives a range for the build; take 15 to 25 percent of that figure as the yearly maintenance line, so you budget both at once. For how maintenance fits into the full life of an app, from brief to launch, read the mobile app development guide.

Was this guide useful?

Questions

Frequently asked.

Can I stop paying for maintenance once the app is stable?

You can stop adding features, but not stop maintaining. Apple and Google change their requirements every year, and an app that misses them cannot ship updates, then starts to break on new phones. The minimum is a yearly update to the current SDK and target API, plus fixes for whatever the new OS versions break.

Is app maintenance more expensive than website maintenance?

Usually, yes, as a share of the build. A website changes when you change it. An app has two platform owners who set deadlines every year, two stores whose policies change, and a native toolchain that must be kept current. A company website can often be maintained for a few hours a month; an app needs a planned update cycle.

What happens to my app if the agency that built it disappears?

If the developer accounts, the code repository and the backend hosting are in your company's name, another developer can take over, usually after a week or two of getting to know the code. If they are in the agency's name, recovering them is slow and sometimes impossible. Check ownership now, while everyone is still answering emails.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.