What App Maintenance Really Costs After Launch

The launch invoice is the one founders plan for. The second invoice, the one that arrives every month after launch, is the one that surprises them. Apps don't stay finished: operating systems change every year, app stores move their requirements, libraries go out of date and users find bugs nobody else did.

App maintenance cost is predictable once you know what's in it. This guide breaks down what you'll actually pay for after launch, the yearly deadlines you can't skip, a worked budget, and how to keep the number from creeping.

Key takeaways

• Plan 15 to 20% of the original build cost per year for maintenance, as a common rule of thumb, plus hosting and third-party services.
• Some work is mandatory: Apple's yearly SDK and Xcode requirements, and Google Play's target API deadline (Android 16, API level 36, from 31 August 2026).
• Skipping maintenance doesn't save money. Upgrades postponed for two years cost far more than the same upgrades done in small steps.
• Store fees are small: $99 a year for Apple's developer program and a one-time $25 for Google Play.
• A monthly retainer is usually the cheapest way to keep an app healthy, because small, regular work avoids emergencies.

What "maintenance" actually includes

New features are not maintenance. Keep them on a separate budget, or the maintenance line will look out of control when it's really product growth.

The yearly deadlines you can't skip

Google Play target API level. Each year Google raises the minimum target API level. From 31 August 2026, new apps and updates must target Android 16 (API level 36). Miss it and you can't ship updates, and apps that fall further behind stop being shown to users on newer Android versions.

Apple's SDK requirement. Apple periodically requires that apps uploaded to App Store Connect are built with a recent Xcode and iOS SDK. When that happens, your app needs to build cleanly on the new toolchain, which often means framework and library upgrades.

Expo SDK and React Native support windows. Expo ships around three SDK releases a year, each pinned to a React Native version. Staying within a couple of SDKs of the latest keeps upgrades small and keeps you on libraries that still receive fixes.

A worked yearly budget

For an app that cost about $40,000 to build, with a backend and payments:

The ranges are wide because traffic, media storage and your choice of services move them. Apps with video, real-time chat or large user bases pay more for infrastructure.

Why skipping maintenance costs more

Upgrades compound. Moving one Expo SDK version is usually a day or two of work. Moving four at once means several breaking changes stacked on top of each other, old libraries that no longer exist, and native build failures that are hard to diagnose.

The same is true for React Native itself. Apps still on the old architecture had to migrate when React Native 0.82 made the New Architecture the only option. Teams that had upgraded steadily did it as one more step. Teams that hadn't faced a project.

From the field: I've migrated eight apps to the New Architecture and cut load time by about 60% along the way. Those migrations are far smoother when the app is already on a recent React Native version, which is exactly what steady maintenance buys you.

How to keep maintenance predictable

1. Use a retainer with a fixed monthly budget and a clear list of what's included: upgrades, fixes, compliance, monitoring.
2. Upgrade on a schedule, for example one Expo SDK step every release cycle, rather than when something breaks.
3. Turn on crash reporting and alerts, so bugs are found by tools, not by one-star reviews.
4. Keep dependencies lean. Every library you add is one more thing to upgrade.
5. Automate builds and releases, so shipping a fix is a routine, cheap event.
6. Track store deadlines in a shared calendar: Google's target API date, Apple's SDK requirement, certificate expiry.

Retainer, hourly or in-house?

FAQ

How much does app maintenance cost per year?

A common rule of thumb is 15 to 20% of the original build cost per year for maintenance work, plus hosting and third-party services. For an app that cost $40,000, that's roughly $6,000 to $8,000 of work, plus infrastructure, depending on traffic and features.

What happens if I don't maintain my app?

It gradually stops working well. New OS versions expose bugs, libraries stop receiving fixes, and you eventually can't ship updates because of store requirements, such as Google Play's yearly target API level. Catching up after a long gap is much more expensive than steady maintenance.

Do I have to pay Apple and Google every year?

Apple's Developer Program costs $99 a year to keep your apps on the App Store. Google Play charges a one-time $25 registration fee. Both also take a commission on in-app purchases and subscriptions.

Is a maintenance retainer worth it?

For most apps after launch, yes. A retainer makes the cost predictable, gets upgrades done before they become urgent, and means someone who knows your code is available when something breaks. Pay-per-fix only works for very simple, stable apps.

Next steps

If your app has been launched for a while and hasn't had an upgrade in months, I can audit where it stands and give you a fixed plan to catch up. Get in touch, or see my services.

Sources

• Target API level requirements for Google Play apps, Google
• Apple Developer Program, Apple
• Expo changelog, Expo
• React Native releases, React Native