Mobile App Maintenance: What Needs Attention After Launch?

Mobile App Maintenance: What Needs Attention After Launch?

After launch, an app needs attention in five areas: crashes and errors, store requirements that actually apply to it, real security problems, compatibility between your server and the app versions people still use, and what users tell you. That is maintenance. Upgrading every library and tool whenever a new version appears is not: a working app doesn't get better because its components have newer version numbers, and every change brings its own risk of new bugs. Changes should have a reason. Below are the reasons that come from outside your control – the ones worth knowing in advance.

1. Crashes and errors: watch, then fix what affects people

Both stores collect stability data from users who agree to share it. On Google Play, Android vitals tracks the user-perceived crash rate and ANR ("app not responding") rate against "bad behaviour" thresholds: for crashes, 1.09% overall and 8% on any single phone model; for ANRs, 0.47% overall and 8% per phone model. If an app exceeds them, Google Play may reduce its visibility and show users a warning on the store listing. Play assesses the last 28 days, flags emerging issues and can send email alerts. Apple reports crashes in App Store Connect, with detailed crash logs in Xcode, and its App Store Improvements page states that apps that crash on launch are removed immediately.

  • Turn on alerts in both consoles and make sure someone reads them – that takes minutes, not a project.
  • Fix the crash groups that affect the most users first, as Google recommends.
  • Watch the server too: API errors, slow responses and failed logins often reveal a problem before reviews do.

2. Store requirements that actually apply

Stores change their rules, and some changes affect apps nobody has touched:

RequirementWhat it means for you
Google Play target API levelNew apps and updates must target Android 16 (API level 36) or higher (deadline 31 August 2026, extensions to 1 November 2026). Existing apps must target at least Android 15 (API level 35) to stay available to new users on devices with newer Android versions. An app below the line keeps working for people who already have it, but new users on new phones may not find it.
Apple SDK minimumApplies when you upload a build: since 28 April 2026, Xcode 26 and the iOS 26 SDK; Apple has announced the iOS 27 SDK as the minimum from April 2027. The version already in the store isn't affected, but your next update – even an urgent fix – must meet the minimum in force at that time.
Apple's outdated apps processApps not updated in three years that have been downloaded not at all or extremely rarely over a rolling 12 months may get a notice; you then have 90 days to submit an update, or the app is removed from the store until you do. Existing users keep a working app.
DeclarationsApple's privacy details and Google's Data safety form must stay accurate when your data practices change; Apple lets you update its answers without a new app version. Google Play's trader status declaration is due by 1 February 2027 for existing accounts.

Raising the target API level isn't just changing a number. Android applies some behaviour changes only to apps that target the new level: for apps targeting Android 16, for example, the opt-out from edge-to-edge display no longer works, and on large screens (600dp and wider) orientation and resizability restrictions are ignored. The change needs testing on real devices. Plan it when the store announces the deadline, rather than discovering it on the day you need to ship a fix.

3. Security: act on real issues

  • Know what the app contains. Keep a list of the libraries and SDKs in the app and on the server. The OWASP Mobile Top 10 2024 includes "Inadequate Supply Chain Security" – risk that arrives through third-party code – alongside insecure data storage and insecure communication.
  • Fix vulnerabilities that apply to you. When a vulnerability is published for a component you use, check whether your app uses the affected part and is exposed. If it is, update that component; if it isn't, record why and move on.
  • Watch for scheduled changes. Some are announced in advance: in 2025, Apple's push notification service switched to new server certificates, and servers sending notifications had to trust the new root certificate. Notices like this arrive by email and in the developer news – someone must read them.
  • Many fixes belong on the server. Logins, permissions and access to data are enforced by the API, and a server fix reaches every app version at once, without waiting for store review.

Components that are no longer supported by their maintainers stop receiving security fixes. Keep that in mind when choosing them – it's not a reason to upgrade working code every month.

4. Old app versions and your server

Not everyone updates. Google's documentation on in-app updates notes that while some users have background updates turned on, others need to be reminded. At any moment, several versions of your app talk to your server, and the server must keep serving every version you still support:

  • Change the API without breaking it. Add new fields and endpoints instead of renaming or removing old ones, and keep the old behaviour while old versions are in use.
  • Know which versions are out there. If the app sends its version number with its requests, the server can see which versions are still in use – and when an old endpoint can finally be retired.
  • Have a way to ask for an update. A minimum-version check lets the server tell users of a too-old version to update. On Android, Google Play's in-app updates offer a flexible flow, which downloads in the background while the app is used, and an immediate full-screen flow meant for updates that are critical to the app's core functionality.

The auto-data.net app is an example. auto-data.net is a specifications catalogue for more than 57,000 cars, with Android and iOS apps and a paid API fed from the same database. Its API is kept backwards compatible, the app reports its version, and the server can show users a message asking them to update if that is ever needed. Server-side fixes help here too: when an Italian user found the app staying in English because the language code reaching the API had changed from "it" to "it,it-IT,it-CH", the fix was to normalise language codes in the API rather than to change the app. More on this setup in one API for a website and a mobile app.

5. What users tell you

Reviews and support messages are the cheapest source of maintenance priorities. Apple suggests that if you can't reply to every review, you prioritise the lowest ratings and reviews that mention technical issues with the current version, and that you mention fixes in your release notes – replying once a fix ships can win back dissatisfied users. Group requests by theme: three people reporting the same confusing screen matter more than one loud request for a new feature.

A realistic rhythm

WhenWhat
ContinuouslyCrash and error alerts from the consoles and the server; store emails read and passed on
MonthlyStability trends, reviews and support themes; which app versions are still in use
When a vulnerability is publishedCheck whether a component you use is affected; fix it if you're exposed
When a store deadline is announcedTarget API level or SDK change: update, test on real devices, release gradually
When data collection changesUpdate the privacy details and Data safety form

New features are a separate decision with their own budget. What maintenance needs is a project that can ship a fix quickly: documented build steps, signing keys and store accounts owned by your company, and access for more than one person. If someone else built the app, our software handover checklist covers what you need. Releasing updates gradually limits the damage of a bad release – see the rollout section in planning your first app release.

If your app is live and you're not sure where it stands – which versions are in use, whether it meets the current store requirements, what the crash reports say – a short review is a good first step – it may show that less needs doing than you feared. Read about our mobile app development work, or contact us with what you have.

Sources

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.