The platforms move every year
Apple and Google ship major platform releases every year. The app is tested and patched before your users update, not after.
Keep your app working after launch.
Apple and Google change the rules every year, whether or not you ship. Maintenance keeps a live app current, month to month, so it never needs a rescue. It starts at $2,000 a month.
Month to month for apps we built or fixed. An app we did not build starts with an onboarding month, so we understand the code before we are responsible for it.
Starting investment
Maintenance starts at $2,000 a month.
That covers a live app's routine care: OS updates, store requirement changes, security and dependency updates, crash monitoring, keeping the backend and APIs the app relies on healthy, and releases when they are needed. It is month to month.
For an app we did not build or fix, the first month is $4,000 while we learn the codebase, the build pipeline and the store accounts, then $2,000 a month after that, with a three-month minimum. A CAM Software audit replaces the onboarding month when maintenance starts within 60 days of it.
Why a working app still needs care
Nothing in the code has to change for the app to fall behind.
Store rules change under you
Apple and Google add requirements, raise target API levels and change privacy disclosures. An app that falls behind gets rejected or hidden.
Things quietly expire
Certificates, push notification keys, developer accounts and subscription settings all expire or change. Each one can take a working app offline.
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: apps that target an older version of Android are already hidden from new users on newer phones, and Google's extension window for this year's requirement closes on 1 November 2026.
How it runs
Maintenance in four parts
- 1.Onboarding, only for apps we did not build or fix. One month to learn the code, the backend, the build pipeline and who owns the store accounts. Skipped after a CAM Software build or fix, or within 60 days of a CAM Software audit.
- 2.Monthly care. OS updates, store requirement changes, security and dependency updates, crash monitoring, the backend and APIs the app relies on, and releases when they are needed.
- 3.A short monthly summary. What changed, what is current, and what is coming due next, so the next deadline is not a surprise.
- 4.Bigger work, quoted first. Major upgrades and new features get a fixed quote before any work starts.
What maintenance does not cover
- New features. Those are quoted as additions, 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. Web and backend work that serves the app is quoted as a fix.
Common questions
Do I have to sign up for a year?
No. Maintenance is month to month. The only minimum is three months, and only for an app we did not build or fix.
Why does the first month cost more for an app you did not build?
Because we have to learn somebody else's code, build pipeline and store accounts before we can be responsible for them. A CAM Software audit already did that work, so it replaces the onboarding month when maintenance starts within 60 days of it.
Can you maintain an app somebody else built?
Yes. That is what the onboarding month is for.
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, and the app is left in better shape than we found it, so whoever comes next starts ahead.
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.