App maintenance
App Maintenance Cost: What Keeping an App Alive Really Costs
App maintenance cost in 2026: realistic monthly ranges, the store rules that make upkeep mandatory, and what 18,055 audited apps say neglect actually costs.
Short answer
Plan for 15-25% of the original build cost per year, with a practical floor of $300-$800 a month for a small production app. The bill covers OS and SDK updates, store-policy compliance, dependency patches, crash triage and review response — and both stores now penalise apps that skip it.
What maintenance actually costs
The industry shorthand — 15-25% of build cost per year — holds up reasonably well in practice, but it hides a floor: below a certain spend, an app is not being maintained at all, just left switched on. These tiers reflect what the work costs when someone is genuinely on the hook for it.
| Tier | Monthly cost | What it buys |
|---|---|---|
| Minimal upkeep | $300 - $800 | Dependency and OS compatibility updates, store-policy compliance, crash monitoring, small fixes |
| Active maintenance | $800 - $2,500 | Everything above plus billing-library upkeep, review response, performance work, a monthly release |
| Growth support | $2,500 - $6,000 | A part-time team: A/B experiments, feature iterations, analytics, proactive refactoring |
The stores made maintenance mandatory
Maintenance used to be a quality choice. Both stores have since turned it into a survival requirement.
Apple removes outdated apps. Under its App Store Improvements process, apps that have not been updated within roughly three years and fall below a download threshold get a 90-day notice, then removal. Google Play raises its minimum target API level every year with a published cut-off — fall behind and the app stops being installable on newer devices, then loses ranking on the devices that remain.
The scale of quiet neglect shows in our audited catalog. Of 18,055 apps (snapshot: 6 August 2026), 23.9% have not shipped an update in over six months, 10.9% in over a year, and 5.2% in over two years. Every app in that last group is one policy sweep away from disappearing, taking its install base with it.
What neglect looks like in the complaint data
The two biggest maintenance line items map directly onto the two biggest complaint clusters in the catalog.
Device compatibility is the #1 recurring complaint, present in 26.8% of audited apps — the direct product of OS releases breaking apps that nobody re-tested. Payment problems are #2 at 24.9%, and a meaningful share of those trace to billing libraries that stores force-deprecate on a schedule. Neither cluster is exotic: both are what skipped maintenance looks like from the user's side of the screen.
That is also why we treat update cadence as a maintenance-risk signal in every report we publish — an app's last-updated date predicts the shape of its next hundred reviews better than its star rating does.
The line items inside the invoice
A credible maintenance quote itemises. If a bidder cannot tell you which of these they cover, the low price is an absence of scope, not efficiency.
- OS and device compatibility — testing and fixes for each annual iOS and Android release, plus the mid-year device quirks
- Store compliance — target API bumps, privacy declarations, policy responses; missing a deadline can unlist the app
- Billing upkeep — payment and subscription library versions, renewal edge cases, refund handling
- Dependency and security patches — the quiet majority of the work, and the part that prevents the emergency rebuild
- Crash triage and monitoring — watching vitals so a bad release is caught in hours, not in the review section
- Review response — replying to users; in our catalog, 60.4% of apps have never answered a single review
Repair, retainer, or rebuild
The 15-25% rule assumes a healthy codebase. It breaks at both ends.
An app that has already gone dark for two years usually needs a one-time repair engagement before any retainer makes sense — the backlog of OS versions, API deprecations and dead dependencies is a project, not a subscription. We wrote about that decision in detail at /blog/repair-or-rebuild-a-broken-app, including when patching a very old codebase costs more than replacing it.
At the other end, an actively growing app outgrows maintenance pricing entirely: past a certain release tempo you are buying development capacity, and pretending it is maintenance just hides the real burn rate.
If you are unsure which situation an app is in, its public signals usually answer the question — update history, complaint clusters and store-policy exposure are all visible from the outside. Our free audit at /app-audit reads exactly those, and a scoped conversation at /contact can turn the result into a concrete monthly number.
Clear answers
Frequently asked questions
How much does app maintenance cost per month?
A small production app needs $300-$800 a month at minimum. Active products typically run $800-$2,500, and growth-stage apps $2,500-$6,000. Annually, 15-25% of the original build cost is a sound planning figure for a healthy codebase.
What does an app maintenance fee actually include?
OS and device compatibility work, store-policy compliance including target API updates, billing-library upkeep, dependency and security patches, crash monitoring and triage, and review response. Anything less is hosting with extra steps, not maintenance.
What happens if I stop maintaining my app?
Apple removes apps left un-updated for around three years under App Store Improvements, and Google Play restricts apps that miss its annual target API deadline. Before removal, the damage shows in reviews: device-compatibility and payment complaints are the two most common clusters across our 18,055 audited apps.
Is the 15-25% of build cost rule accurate?
As a planning range for a healthy codebase, yes. It underestimates apps that have been neglected for years — those need a one-time repair project first — and overestimates very simple apps, which can sit at the $300-$800 monthly floor instead.
Should I pay a monthly retainer or fix things as they break?
Retainers win for production apps because the expensive failures are the preventable ones: a billing deprecation caught on schedule is an hour of work, the same deprecation in production is a revenue outage. Fix-on-failure only suits apps you are prepared to lose.