Skip to content

Odduel

We put the odds in your favour

Insights

App maintenance cost: what you pay for after launch

What app maintenance includes, what drives its yearly cost, how to estimate and control it, and the items most often forgotten when budgeting after launch.

A developer's hands on a laptop keyboard beside two test phones on a wooden desk, updating an app after launch

App maintenance cost is the ongoing spend that keeps a released app working, secure and accepted by the app stores: operating system updates, bug fixes, hosting, third-party services, monitoring and small improvements. It is not a one-off line but a yearly budget, and its size depends far more on how the app was built and what it connects to than on how many screens it has. This guide explains what maintenance includes, what drives the cost, how to estimate and control it, and what is most often forgotten.

Last updated: 11 November 2026.

What does app maintenance actually include?

App maintenance is the work and the services needed to keep an app running as intended after launch, without adding major new features. It sits between “doing nothing” and “building version two”.

In practice it covers six groups of work:

  • Compatibility: updating the app for each new iOS and Android release, new devices and new screen sizes.
  • Store compliance: meeting new rules from Apple and Google, such as the yearly target API level requirement on Google Play, privacy labels and review guideline changes.
  • Fixes: bugs found by users, crash reports and edge cases that only appear at scale.
  • Security: updating libraries and frameworks, renewing certificates and closing known vulnerabilities.
  • Infrastructure: servers, databases, file storage, push notifications, email and backups.
  • Small improvements: copy changes, minor design adjustments and performance work.

At Odduel, a creative and technology agency in Barcelona and São Paulo, we plan maintenance during the build of every project in our application development service, because decisions made in the first weeks set the running cost for years.

In short: maintenance is a yearly budget, not an afterthought. Its size is driven by the platforms you support, the number of integrations, the age of the technology, the hosting set-up and how much change the business asks for. A clear scope, a shared codebase and good monitoring keep it predictable.

How much does app maintenance cost per year?

There is no honest single figure, because two apps with the same number of screens can need very different levels of care. You will often read a rule of thumb that expresses yearly maintenance as a share of the original build cost. It is a useful starting point for a conversation, but it hides the real drivers: an app with a payment provider, a booking system and a custom back end will always need more than a content app with a static API.

A better way to think about it is in layers:

  1. Fixed running costs: developer accounts, hosting, monitoring tools and paid services. These arrive every month or year whatever happens.
  2. Mandatory work: operating system releases, store rule changes and security updates. You cannot skip these without the app degrading or being removed.
  3. Reactive work: bug fixes and support. This shrinks as the app matures, if the code is tested.
  4. Elective work: improvements the business wants. This is the most flexible layer and the one to plan deliberately.

The first two layers are the floor. The last two are where most of the variation between apps comes from.

What drives app maintenance cost?

The main app maintenance cost factors are structural. They are set by choices made before and during the build, which is why they are worth discussing early.

Number of platforms and codebases

An app built separately for iOS and Android has two codebases, so every change is made twice and tested twice. A cross-platform framework shares most of the code, which usually reduces maintenance effort, though some platform-specific work remains. A web app or progressive web app has no store review at all, which removes a whole category of work.

Integrations and third-party services

Every connection to an outside system is a dependency that can change without notice: payment providers, maps, analytics, CRM, ERP, login providers and messaging services. Each one updates its API, retires old versions and changes its terms. Integrations are often the single largest source of unplanned work.

Age and health of the codebase

Code that was written quickly, without tests or documentation, costs more to change safely. Outdated frameworks also become harder to update the longer they are left. A codebase that is updated little and often stays cheap; one that is left for two years needs a large catch-up.

Back end and hosting

A serverless or managed back end shifts some maintenance to the provider, while a custom server needs operating system patches, scaling and backups. Usage also matters: more users mean more data, more storage and more support requests.

Regulation

European apps carry legal duties that need occasional work: consent flows and data requests under the General Data Protection Regulation, accessibility for many consumer services, and changes in store terms in the EU. These are rarely large jobs, but they must be budgeted.

FactorLower maintenanceHigher maintenance
PlatformsOne shared codebase or a web appSeparate native iOS and Android apps
IntegrationsFew, stable, well-documented servicesMany services, custom or legacy systems
CodebaseTested, documented, current frameworkUntested, undocumented, outdated framework
Back endManaged servicesCustom servers run in-house
Change requestsPlanned in a quarterly roadmapAd hoc requests every week
The main drivers of app maintenance cost and what pushes each up or down.

How do you estimate app maintenance cost?

An app maintenance cost estimate is built from the layers above, not from a percentage. Here is the process we follow with clients:

  1. List every running service with its billing model: developer accounts, hosting, databases, email, push notifications, monitoring, analytics and any paid API.
  2. Count the dependencies: frameworks, libraries and integrations. Each one is a source of future updates.
  3. Map the release calendar: Apple and Google publish major operating system versions every year, so plan a compatibility window for each.
  4. Estimate reactive work from the app’s age and test coverage. A new app needs more fixing in its first months; a stable one less.
  5. Agree a pot for improvements: a number of days per month or quarter, decided by the business, not by accident.
  6. Add a contingency for surprises, such as an integration partner retiring an API.

The result is a yearly plan with a fixed part and a flexible part. A good supplier will quote the fixed part clearly and explain how the flexible part is used and reported.

What is often forgotten when budgeting for app maintenance?

Most surprises come from the same short list:

  • Developer and store accounts that must be renewed every year.
  • Certificates and keys for push notifications and signing that expire.
  • Domain names and email services behind password resets and notifications.
  • Data growth: storage and backup costs rise quietly with each user.
  • Design debt: a new phone size or a new system font can break layouts that were never tested for it.
  • Content: someone has to update texts, prices and pictures inside the app.
  • Knowledge: if only one developer understands the code, losing them is the largest cost of all.

Write these into the plan from the start. They are rarely large on their own, but together they explain why “the app was finished” and “the app costs nothing now” are not the same thing.

How can a business keep app maintenance cost under control?

Keeping maintenance predictable is mostly a matter of discipline rather than budget:

  1. Choose the stack for the long term. A widely used framework has more developers, more documentation and longer support.
  2. Keep the number of integrations honest. Each one should earn its place.
  3. Update little and often. Monthly dependency updates are cheaper than a yearly rescue.
  4. Invest in automated tests and crash reporting. They make every change safer and faster.
  5. Document the system: architecture, accounts, credentials storage and release steps.
  6. Plan improvements as a roadmap, reviewed every quarter, so requests are weighed against each other.
  7. Own your accounts and code. The store accounts, the repository and the cloud accounts should belong to your company.

Maintenance is also a good moment to remove what nobody uses. Deleting a little-used feature is often the cheapest way to cut future work.

Nothing To Eat ordering screens by Odduel on several phones, the kind of app interface that needs updates after launch

Maintenance contract or pay as you go?

There are two common ways to buy maintenance, and each fits a different kind of app.

ModelHow it worksSuits
RetainerA fixed monthly number of hours or a defined scope, with response timesApps that earn revenue or support daily operations
Pay as you goWork is quoted and invoiced job by jobSimple apps with few integrations and low change
HybridA small fixed base for mandatory work, plus quoted improvementsMost growing businesses
Common maintenance models compared.

A retainer buys availability: someone knows the code and can respond quickly when a store rejects an update or an integration fails. Pay as you go can look cheaper, but each job starts with relearning the system. Whatever the model, ask for a monthly report of what was done and why. Our guide on how to choose an app development company lists the questions to ask about support before you sign.

When does maintenance become a rebuild?

At some point the cost of keeping an old app alive can exceed the cost of rebuilding it. Signs include a framework that is no longer supported, a codebase nobody wants to touch, store rejections that keep returning and features that take weeks instead of days. If you recognise these, compare a planned rebuild against two or three more years of maintenance. Our app development timeline explains how long a rebuild typically takes in phases, and the MVP development guide shows how to restart with a smaller, cleaner scope.

Questions people ask

What is app maintenance?

App maintenance is the ongoing work that keeps a released app working, secure and compliant: updates for new iOS and Android versions, store rule changes, bug fixes, library and security updates, hosting and third-party services, plus small improvements. It does not include major new features, which are usually planned and quoted as separate development work.

How much does app maintenance cost per year?

It depends on the platforms supported, the number of integrations, the health of the code, the hosting set-up and how much change the business wants. Rules of thumb based on a share of the build cost exist, but a reliable estimate lists running services, mandatory updates, expected fixes and a planned budget for improvements.

Can I stop maintaining my app?

You can, but the app will degrade. New operating system versions can break features, stores can remove apps that miss their requirements, and outdated libraries leave security holes. If an app is no longer needed, retiring it properly is better than leaving it unattended, including removing user data in line with the GDPR.

Is maintenance cheaper for a cross-platform app?

Usually, because most code is shared, so each change is made and tested once rather than twice. Some platform-specific work remains, such as native modules and store submissions for each platform. A web app or progressive web app avoids store reviews entirely, which removes another category of maintenance work.

Who should own the app accounts and code?

Your company should. The Apple and Google developer accounts, the code repository, the cloud hosting and every paid service should be registered to the business, with the supplier given access. This keeps you free to change supplier and avoids losing the app if a relationship ends.

Start by listing every service and dependency your app relies on: it is the base of any honest maintenance budget. If you want an app planned for a predictable running cost, or a review of an app you already have, see our application development service or tell us about your app.

More articles

More from our Insights.

Explore all insights

Get in touch

Let’s change your odds.

Odds do not change on their own. If you have something to build, launch or fix, tell us about it and we will show you how we would approach it.

    Need an NDA before you share details? Start a project

    Chat with us