Mobile app maintenance services that keep your app in the stores
Mobile app maintenance services for companies whose app has to keep working after launch. Apple and Google change their rules every year, iOS and Android release new versions, libraries go out of support and users find the crash nobody saw in testing. We keep your iPhone and Android app updated before each store deadline, fix what breaks and report what we did, on a monthly plan you can cancel with one month's notice. The code and the store accounts stay in your company's name.
- No lock-in: cancel with one month's notice
- Scope agreed in writing before work starts
- Accounts and logins in your company's name
Why an app that works today still needs maintenance
A website can run for years on the same code. A mobile app cannot, because it lives on platforms that its owner does not control. Each year Apple and Google release a new operating system, raise the minimum tools an upload must be built with and retire older libraries. None of this is announced to your users, and none of it breaks the app on the day it happens. It shows up later, on the day you need to ship an urgent fix and discover that the project no longer builds, the store refuses the upload or a payment library is past its deadline.
Mobile app maintenance is the work that keeps the app ready to update at any time. Done monthly, it is a small and predictable job. Left for two or three years, it becomes a project of its own, often larger than the change you wanted to make.
The store rules that set the calendar
Most maintenance work follows dates set by Apple and Google. These are the current ones, from their own pages, read on 11 November 2026:
| Rule | What it requires |
|---|---|
| Apple SDK minimum | Since 28 April 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later, using the SDK for iOS 26 or the matching platform |
| Apple deployment target | Since 9 September 2026, iOS and iPadOS apps uploaded must target iOS 13 or later |
| Google Play target API level | From 31 August 2026, new apps and app updates must target Android 16 (API level 36); existing apps must target Android 15 (API level 35) to stay available to new users on newer Android versions |
| Google Play Billing Library | Every version has a two-year deprecation cycle; by 31 August 2026 new apps and updates must use version 8 or later, with an extension possible to 1 November 2026 |
| Apple App Store improvements | Apps not updated within the last three years that fail a minimal download threshold can be flagged for removal, with 90 days to submit an update |
The table changes every year, so a maintenance plan has to be based on the rules as published at the time, not on a list written at launch. We keep a calendar of these dates for every app we maintain and plan the update months before the deadline, not in the last week.
What our mobile app maintenance covers
- Yearly OS and SDK update. When a new iOS and Android version arrives, we build the app with the new tools, test it on the new system and fix what changed, before your users install the update.
- Store deadlines. Target API level, SDK minimums, billing library versions and policy declarations, handled before the date in the table above.
- Dependency and security updates. Libraries and SDKs updated on a schedule, with security fixes applied as soon as they are published. Apple requires a privacy manifest for apps and listed third-party SDKs, so each SDK update is checked against it.
- Crash monitoring and fixes. Crash and error reports read every week, the worst problems fixed first, and the fix confirmed in the next report.
- Backend and integrations. Server updates, certificates, push notification keys and the outside interfaces the app depends on, so a renewed key or a changed partner interface does not silently stop the app.
- Store listing and forms. Privacy details, data safety form, age rating questions and screenshots kept true to the app as it is today.
- Small changes. A fixed number of hours each month for text changes, small fixes and improvements, agreed in writing.
- A monthly report. What was updated, what was fixed, what is coming next and which deadline is closest, in plain language.
Maintenance, support and new features are different things
A maintenance plan works best when everyone knows where it ends. Maintenance keeps the existing app healthy and inside the rules. Support answers questions from your team or your users. New features change what the app does, and they are scoped and priced as their own piece of work. Mixing them up is how maintenance budgets disappear: the hours go on a new screen and the SDK update waits until the deadline. We keep the three apart in the written plan, so the yearly update is never the thing that gets pushed back.
Taking over an app another team built
Many of the apps we are asked to maintain were built by someone else: an agency that moved on, a freelancer who is no longer available or an in-house engineer who changed jobs. The first step is a handover review, done before any monthly plan starts:
- Access. Source code repository, App Store Connect and Google Play Console access, signing certificates and the Android upload key, backend hosting and the accounts behind push notifications and analytics.
- A clean build. We build the app from its source code on a clean machine. If it does not build, that is the first finding, and usually the most important one.
- The gap list. Every outdated tool, library and store requirement, with the deadline that applies to it and what it takes to fix.
- A written plan. First the catch-up work needed to reach a current state, quoted separately, then the monthly plan that keeps it there.
If a signing key or part of the source code is missing, we say so plainly in the review and list the options. Sometimes the app can be recovered and sometimes a part has to be rebuilt; you decide with the facts in front of you.
For business systems behind an app, see software maintenance; our technical debt guide explains how to plan the catch-up, and our app launch guide covers the first release.
Why the yearly update is worth doing early
Apple and Google publish beta versions of each new operating system months before release. Testing the app on the beta is where most maintenance problems are found while they are still quick to fix, because nothing is broken for users yet and there is no deadline next week. It is also when permission prompts, background limits and privacy rules change, and those changes often need a small adjustment to what the app tells users. A team that waits for the public release has to fix the same problems while users are already reporting them. We test on the beta and keep the fix ready for release day.
Proven on our own apps
We build and run our own apps on the App Store, and they go through the same yearly cycle: new Xcode, new SDK, new privacy rules and new store forms, every year. The maintenance calendar we use for clients is the one we use for our own apps, so every rule in the table above is one we have already met in practice.
How a maintenance plan starts
- Brief. Tell us which app, which platforms and who built it. We reply within one working day.
- Handover review. Access, clean build and the gap list, as above.
- Written plan. Scope, severity levels, monthly hours and any catch-up work, agreed before the plan starts.
- Monthly cycle. Updates, monitoring, fixes and the monthly report, with the next store deadline always on the first line.
You own it
The source code stays in your company's repository, the store accounts and signing keys are in your company's name, and we work with access you grant and can withdraw. Backends we maintain run in an EU data region under a written data processing agreement. The plan can be cancelled with one month's notice, and you keep everything.
Before a release, see mobile app testing. For the build itself, see app development, iPhone app development and Android app development. For the yearly cost of an app, see our guide to how much app development costs. For websites, see WordPress maintenance. See prices. For the server side, see backend app development.
Questions we get
Does an app really need maintenance if nothing is broken?
Yes, because the stores move even when the app does not. Apple sets a minimum Xcode and SDK version for every upload, and Google Play sets a minimum target API level each year and a deprecation cycle for its billing library. An app that is not updated can no longer receive a fix quickly when it is needed, and on Google Play it stops reaching new users on newer Android versions.
Can you maintain an app another team built?
Yes. We start with a handover review: we build the app from its source code on a clean machine, check the store accounts, signing keys and dependencies, and list what is out of date. If the source code or a signing key is missing, we say so in writing before the plan starts, with the options.
What is included in a monthly plan?
A written scope: the yearly OS and SDK update, store deadlines, dependency and security updates, crash monitoring and fixes, store listing and policy forms, and a fixed number of hours for small changes. New features are quoted separately, so maintenance hours are not used up by feature work.
How fast do you react to a crash or a store rejection?
Severity levels and the escalation path are part of the written plan. A crash affecting many users or a rejection that blocks an urgent fix comes first. We watch the crash reports and store messages ourselves, so we usually see the problem before your users report it.
Who owns the app while you maintain it?
Your company. The source code stays in your own repository, the App Store and Google Play accounts are in your company's name, and we work with access you can withdraw at any time. You can end the plan with one month's notice and keep everything.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.