Mobile App Maintenance: The Costs After Launch

After launch, a business app needs ongoing maintenance: updates for new iOS and Android versions, changes required by app store policies, security patches, server and hosting costs, monitoring, bug fixes, and small improvements. A common planning figure is 15 to 20 percent of the original build cost per year, though it varies with the app's complexity and how actively it is developed.

Many businesses budget for the build and nothing after it. Then a new operating system version breaks a feature, or a store policy deadline passes, and the app stops working or is removed from the store.

What maintenance includes

Platform updates

Apple and Google release major operating system versions every year, and devices change screen sizes and capabilities. Apps must be tested and often updated to keep working and to meet minimum target versions required by the stores.

Store policy changes

Both stores regularly add requirements around privacy declarations, permissions, account deletion and target versions, with deadlines. Missing them can block updates or remove the app.

Dependency and security updates

Apps rely on libraries for maps, payments, notifications and more. These need updating for security fixes and compatibility.

Back end and hosting

Servers, databases, storage, notification services and SMS or WhatsApp messaging all have running costs, and need monitoring and updates.

Monitoring and bug fixes

Crash reporting and performance monitoring show problems real users hit. Fixes should ship quickly.

Improvements

Once people use the app, they ask for changes. A small, steady stream of improvements keeps adoption high.

Typical cost components

| Component | Nature of cost | | --- | --- | | Developer accounts | Apple yearly fee; Google one-time fee | | Hosting and services | Monthly, grows with usage | | Messaging (SMS, WhatsApp) | Per message | | Maintenance retainer | Monthly, covers updates and fixes | | Improvements | Per change or as a monthly allocation |

Support models

Retainer

A monthly fee covering a set number of hours, response times for issues, and routine updates. Predictable and suits most business apps.

Pay as you go

Work billed when needed. Cheaper in quiet months, but risky around store deadlines and emergencies.

In-house developer

Suits companies with a larger app portfolio or continuous development. Needs backup cover and access to specialist skills.

A maintenance calendar

A simple yearly rhythm keeps most apps out of trouble:

• Monthly: review crash reports and user feedback; ship small fixes.
• Quarterly: update libraries and dependencies; review hosting costs and usage.
• Before each major OS release (usually mid-year for beta, autumn for release): test on beta versions and fix issues before users upgrade.
• When stores announce policy changes: plan the work well before the deadline.
• Yearly: security review, access review for developer and store accounts, and a plan for the next year's improvements.

Reducing maintenance cost

• One cross-platform codebase rather than two native apps. See React Native vs Flutter vs native.
• Keep dependencies few and well chosen.
• Automated tests that catch breakages before release.
• Regular small updates rather than rare large ones.
• Remote configuration for content that changes often, so it does not need a new release.

Signs an app is being neglected

• It has not been updated in the stores for over a year.
• Crash reports are not being reviewed.
• Users on newer phones report layout problems.
• Nobody knows when the next store deadline is.
• The original developer has left and nobody else can build it.

Frequently asked questions

Can we skip maintenance for a stable internal app?

For a while, but not indefinitely. Operating system updates on staff phones will eventually break something, usually at an inconvenient time.

What if our original developer is no longer available?

Commission a code review from a new partner. If you own the code and accounts, the app can be taken over.

Who should own the developer and store accounts?

Your company, always. See app store approval.

How do we budget before launch?

Include a year of maintenance in the business case. See mobile app development cost in India.

Keep your app healthy

Turbo Bytes Consulting builds mobile apps and supports them after launch with clear maintenance agreements, including apps originally built by others.

Book a 30-minute scoping call for an app health check.