Your team is busy building features
Someone still has to keep the app stable while they ship. We watch what they cannot.
Your app works today. Keep it that way.
Maintenance is an engineer and a QA tester watching your app, so problems get caught early, before they cost you customers, revenue or your rating. It keeps a live app, its backend and its store listings current. Maintenance starts at $10,000 a month.
This month, your app
- Package updates built and testedEvery weekday
- Ratings, reviews, crashes and logsWeekly
- Device pass: phones, foldables, tabletsMonthly
- Distribution certificate expires in 21 daysRenew
- New OS betas tested before releaseYearly
Who it is for
Businesses whose app is live, and whose customers, members, staff or drivers use it every day.
You own the app, and someone else builds it
An agency or another team ships the changes. You want an independent check that the app still looks right.
Nobody watches the app day to day
There is no one checking crashes, reviews and store deadlines until something has already gone wrong.
Apps we built or fixed start straight away. Any other app starts with the $8,000 audit, so we know the code before we are responsible for it.
What can go wrong with an app nobody looks after
None of it waits for your roadmap, and most of it shows up in your ratings before anyone on the team notices.
A new OS version arrives every year
iOS and Android both ship a major release every year. Screens, permissions and background behavior can change under an app nobody updated.
New phones and foldables arrive
Your code may work well on them, or it may not, and you will not know unless someone is testing on the right devices.
It falls behind Google's yearly deadline
Google raises its target Android version every year. Apps that fall behind can no longer ship updates, and new users on newer Android phones cannot find them.
An update gets rejected
Apple raises the minimum it accepts, and your customers stay stuck on the old version.
Something quietly expires
Certificates and provisioning profiles expire, and developer memberships and store agreements lapse. Some block your next update. A lapsed Apple membership stops new downloads.
A package update breaks it
The packages inside the app ship updates every few weeks, and one bad update can break sign-in or payments.
Ratings slip quietly
A crash on one device, a slow screen, a confusing update. The one-star reviews arrive before the bug report does.
Small problems become technical debt
Nobody fixes the small things, so they pile up into a project.
How maintenance works
Step 1
Start
If we built or fixed the app, we start straight away. Otherwise the $8,000 audit comes first.
Step 2
Watch and care
We check the app, its crashes, errors, logs and reviews, keep it current, and catch problems while they are still small.
Step 3
Fix it or file it
We fix what we find, or write a clear ticket for your team, whichever you prefer. Every month ends with a short summary of what changed and what is coming due.
Step 4
Bigger work, quoted first
New features and major upgrades get a fixed quote before any work starts.
What moves the monthly price
Maintenance starts at $10,000 a month for one app. These raise it, and each is agreed before you sign.
One codebase or two
A shared app, or one native app, is one codebase. Native apps on both platforms are two.
How much backend we look after
Only the app, or the server, database, APIs and web app around it too.
How often you release
A release a quarter is different from a release every two weeks.
Platform features
Subscriptions, maps, health data, push notifications and sign-in providers all change on their own schedules.
Regulated data
Health or financial records add review and care to every change.
How far behind it starts
The audit tells us. An app that starts far behind may need a fix before maintenance.
Every month includes
Part engineer, part QA: the upkeep an engineer would do, and the checking a tester would do.
- Store ratings and reviews watched for new problems
- Crash, error and log review, so issues are caught before users report them
- Fixes for what we find, or clear tickets for your team, whichever you prefer
- Small bug fixes and technical-debt items from your roadmap, within the month
- OS updates, tested and patched before your users update, not after
- New devices, including foldables, tested as they arrive
- Store requirement changes from Apple and Google
- Security and dependency updates, and a check that no package update broke anything
- Keeping the backend and APIs the app relies on healthy
- Releases when they are needed, and a short monthly summary
What we check, and how often
On weekdays. We test only the platforms and devices your app supports: an Android-only app is not tested on iPhone.
iPhone
Android phone
Foldable (open)
iPad
Android tablet
Every weekday
The code
Security advisories and package updates, built and tested so nothing breaks quietly. Findings turned into fixes or tickets. Small bug fixes and technical-debt items from your roadmap.
Every week
The app in the real world
App Store and Google Play ratings and new reviews. New crashes and errors. Backend error logs and alerts.
Every month
Devices and deadlines
A test pass on iPhone and Android, plus foldables, tablets and wearables where your app supports them. Expiring certificates and profiles, developer memberships and store agreements. Apple and Google policy changes and store forms: privacy details, data safety, age ratings and account deletion. Your monthly summary.
When Apple or Google ship an update
Point releases
Each smaller iOS and Android update is tested when it ships, so a minor OS change does not surprise you.
Every year
Major releases
New iOS and Android versions tested in beta and patched before they ship. New devices tested as they launch. Google's yearly Android version deadline and Apple's yearly minimum for new uploads.
What maintenance does not cover
- New features. Those are quoted at a fixed price before work starts.
- Major framework upgrades, like a React Native architecture migration. Those are quoted as a fix.
- Redesigns, new screens, or rebuilding a backend. Those are quoted as a build or a fix.
- A standalone website with no app behind it.
Maintenance starts at $10,000 a month.
A three-month minimum, then month to month. Apps we did not build or fix start with the $8,000 audit, which is paid on its own. Prices are for remote work. On-site work is quoted separately and priced higher.
Why apps fall behind
Everything around your app keeps moving. An app nobody updates falls behind on its own.
Apple and Google raise their requirements every year. Google requires apps to target a recent version of Android and moves that line forward annually, and apps that fall too far behind stop showing up for people on newer phones. Apple raises the minimum it accepts for new uploads on a similar yearly rhythm.
The packages inside the app move even faster. A React Native app depends on hundreds of open-source packages, and many of them ship updates every few weeks: security fixes, new platform support, breaking changes. Skip a year and one upgrade becomes several, each depending on the others.
Maintenance keeps all of it current a little at a time, so it never piles up into a project.
Right now: Google says support for the Google Fit APIs runs through the end of 2026. If your app still depends on them, plan its migration before support ends.
Source: Android Developers, Google Fit Migration FAQ (checked October 20, 2026) · Content licence.
Common questions
How much does app maintenance cost per month?
It starts at $10,000 a month for one app. More codebases, more backend or more frequent releases raise it, and you agree the price before you sign.
Do I have to sign up for a year?
No. There is a three-month minimum, then it is month to month.
Can you maintain an app somebody else built?
Yes. It starts with the $8,000 audit, so we know the code, the build pipeline and the store accounts before we are responsible for them.
What if something breaks?
Routine fixes are part of the month. Anything larger gets a fixed quote before work starts, so you are never surprised by an invoice.
What happens if we stop?
You keep everything: the code, the store accounts, the signing keys and the documentation. Nothing is held back.
Keep it working.
Twenty minutes is usually enough to tell whether your app needs maintenance, a fix first, or neither.
One less thing to worry about.