Skip to content
Mobile Apps15 min read

Mobile App Maintenance: What Happens After Launch?

What recurs after an app launches: a maintenance worksheet with owners and evidence, plus a dated calendar of Apple, Google Play and React Native deadlines.

01

What does mobile app maintenance involve after launch?

After launch, an app needs a steady list of recurring work: yearly store toolchain upgrades on both platforms, testing on each new OS, framework and SDK updates with matching privacy declarations, policy reviews, account renewals, crash and performance triage after every release, security patches, backend and API changes, tested backups and product improvements. Apple and Google set deadlines on their own schedules, and missing them has concrete effects: an Apple membership lapse removes your apps from every storefront, and an Android app that falls behind Google Play's target API level stops reaching new users on newer devices.

This guide gives you two tools to plan that work: a worksheet of eleven recurring work types with owners and evidence, and a dated compliance calendar built from Apple, Google and React Native's own pages. It does not give prices. Effort depends on what your app contains, and the worksheet shows what drives it.

02

Key takeaways

  • Plan maintenance by work type, owner and evidence, not by a percentage of the build cost.
  • Diary the fixed dates: Apple's membership anniversary, Apple's Xcode minimum (late April in recent years) and Google Play's target API deadline (31 August in 2026).
  • Keep the Apple Account Holder and Play Console owner inside your business. Only the Account Holder can renew Apple membership.
  • React Native maintains only its latest three minor series, so a team that skips upgrades for a year falls out of support.
  • Each SDK you add brings duties: privacy manifests on iOS and an accurate Data safety form on Google Play.
  • Review crash and ANR data after every release. Google Play may reduce the visibility of apps over its thresholds.
03

Why Apps Can't Stand Still

Websites run on servers you control. Apps run on users' devices, governed by operating systems and stores that change on their own schedules. Each year brings new OS versions, new devices, new policy requirements and updated libraries. Maintenance is how an app keeps working in that moving environment.

04

The maintenance planning worksheet

Copy this table into a spreadsheet and fill in the owner column with real names. The 'what makes it bigger' column is how you estimate effort without a price list: the more of those drivers your app has, the more time that row needs. The last column is what you should be able to see when the work is done, which is also what to ask an agency or contractor to show you. Frequencies marked as a pattern are inferences from recent years, not published rules.

Work typeFrequencyOwnerWhat makes it biggerEvidence it was done
1. Store toolchain upgrade (Xcode and SDK on iOS, target API level on Android)Yearly on each platform, before the deadlineLead developerNative modules, old dependencies, custom build scriptsA build on the new toolchain uploaded before the deadline
2. New OS compatibility testingYearly, from the beta to the public release (pattern)QA and developersNumber of devices to test, background tasks, notifications, permissionsA test report on the new OS version
3. Framework upgrade (React Native or Flutter)Each minor release, or at least before support endsLead developerHow far behind you are, third-party native packages, architecture changesThe app runs on a supported version
4. Third-party SDK updates and privacy declarationsWhen an SDK changes, plus a quarterly reviewDevelopers with product or legalNumber of SDKs, especially ads and analytics; how much data is collectedPrivacy manifests, Apple's App Privacy details and Play's Data safety form match the build
5. Store policy reviewQuarterly, and when Google or Apple announces changesProduct ownerRegulated category (finance, health, children), payments, user-generated contentA policy log with the actions taken
6. Accounts and credentials (Apple membership, push keys, signing keys, certificates, domains)Yearly, plus expiry alertsAccount holderNumber of apps and accounts; accounts held by an agencyRenewal dates in a shared calendar
7. Crash, ANR and hang triageWeekly and after every releaseDevelopersRelease frequency, spread of devicesAndroid vitals under Google's thresholds; top issues ticketed
8. Security patches (app dependencies and backend)Monthly scan; urgent fixes as neededDevelopers or DevOpsLogin, payments, personal dataScan report and patched versions
9. Backend and third-party API changes (payments, maps, sign-in providers)As each provider announcesDevelopersNumber of integrationsDeprecation notices tracked with dates
10. Backups and a restore testQuarterly (a sensible default, not a rule)DevOpsData volume, number of regionsA restore actually carried out and recorded
11. Product improvements from analyticsMonthly cycleProduct ownerRoadmap ambitionShipped changes tied to a metric
05

Annual compliance calendar

These are the dates that come from the platforms rather than from your roadmap. Check each source once a quarter, because the platforms announce changes during the year and dates can move.

WhenWhatWhat happens if you miss it
Your membership anniversaryApple Developer Program renewal. Only the Account Holder can renew.Verified: apps and In-App Purchases become unavailable in all storefronts. Installed copies stay on devices, but you lose TestFlight, Certificates, Identifiers & Profiles, the App Store Connect API and Xcode Cloud.
Late April (inferred pattern)Apple's minimum Xcode and SDK version for uploads. Past minimums took effect on 25 April 2023, 29 April 2024 and 28 April 2026; Apple's page lists none for 2025 and none yet for 2027. The late-April timing is our inference from those dates, not an Apple rule.App Store Connect will not accept new builds made with an older Xcode. Since 28 April 2026 that means Xcode 26 with the 26 SDKs.
9 September 2026 (one-off)iOS and iPadOS apps uploaded to App Store Connect must target iOS 13 or later.Builds with an older deployment target are not accepted.
31 August (2026; Google sets a yearly deadline)Google Play target API level for new apps and updates: Android 16 (API 36) in 2026. An extension to 1 November 2026 can be requested.You cannot submit updates until the app targets the new level. Separately, existing apps must target API 35 or higher to stay available to new users on devices running a newer Android version.
Several times a yearGoogle Play policy announcements. Google published one each July from 2023 to 2026, with others in January, April and from October to December. The July 2026 announcement gave at least 30 days to comply with new requirements.Policy enforcement against the app or account; the timescale depends on the policy.
About every two monthsReact Native minor releases. React Native maintains only the latest three minor series. On 15 October 2026, 0.87 and 0.86 were Active, 0.85 was End of Cycle and 0.84 and older were Unsupported.No patch releases for your version, including critical fixes.
From 30 September 2026Android developer verification: protections for installs from participating stores in Brazil, Indonesia, Singapore and Thailand on certified devices running Android 7 or later; global rollout planned for 2027.Matters most for apps distributed outside Google Play. Google says Play automatically registers 99% of apps; check Play Console for any that need manual registration.

Worth noting

Flutter's compatibility policy covers breaking changes and deprecations, but Flutter does not publish a fixed support window in the way React Native does. Treat staying on a recent stable release as part of item 3 in the worksheet.

06

OS and Store Requirement Updates

When Apple and Google release major OS versions, test the app on them, adopt required changes and fix anything that breaks. Google Play requires new apps and updates to target an API level within a year of the latest major Android release. Its rule for existing apps is precise: they must target Android 15 (API level 35) or higher to remain available to new users on devices running a newer Android version, and an app targeting API 34 or lower is only available on devices running that version or lower.

Current examples: apps uploaded to App Store Connect since 28 April 2026 must be built with Xcode 26 and the 26 SDKs, and since 9 September 2026 iOS apps must target iOS 13 or later. From 31 August 2026, new Android apps and updates must target Android 16 (API level 36), with an extension to 1 November 2026 available on request. All of these dates may change; the calendar above lists them together.

07

Dependencies, SDKs and Privacy Declarations

Frameworks like React Native and Flutter, and third-party SDKs, release updates regularly. Falling far behind makes each upgrade harder and riskier. React Native commits to maintaining only the latest three minor series and ships critical fixes as patch versions of those series. Update on a regular cadence, and apply security patches promptly.

SDKs also carry compliance duties. Apple requires privacy manifests for a listed set of commonly used SDKs (including Firebase, Flutter and OneSignal) and signatures for binary dependencies when you add them in a new app or update, and reminds developers that they are responsible for all the code an SDK includes. Google's Data safety form must cover data collected by SDKs too, and Google says discrepancies can lead to blocked updates or removal. Each time an SDK is added or upgraded, check both declarations. The mobile app data privacy guide covers the wider obligations.

08

Monitoring and Crash Reporting

Crash reporting and performance monitoring show what users actually experience. Google Play's Android vitals sets bad-behaviour thresholds for user-perceived crash rate (1.09% overall, 8% per phone model) and user-perceived ANR rate (0.47% overall, 8% per phone model); Google says that above them Play may reduce the visibility of the app and may show a warning on the store listing. Review these numbers after every release.

When users report crashes or slowness, the diagnostic guide to crashes and slow apps maps each symptom to where to look and who owns the fix. For the engineering fixes themselves, see app performance optimisation.

09

Analytics and Feature Improvements

Launch is when real learning begins. Review funnels and feature usage, gather feedback, and prioritise improvements that move key metrics. See mobile app analytics for which metrics to review each month. Each improvement goes through the same design, build and testing discipline as the original release.

10

API Changes

Backend and third-party APIs evolve. Coordinate API changes with app releases, keep supporting older app versions until their usage is low, and use a minimum supported version check to prompt updates when necessary. See mobile app API integration.

11

Hotfixes and Incident Response

Production incidents are part of running an app. Prepare before they happen: staged rollouts so a bad release reaches a small share of users first, server-side feature flags to switch off a broken feature without a new release, a documented hotfix path, and a contact list for the store developer accounts. Apple allows developers to request an expedited review for critical fixes, though approval is not guaranteed. The release management guide covers rollout gates and rollback in detail.

If an incident involves personal information, follow your data breach process. In Australia, businesses covered by the Privacy Act must assess suspected eligible data breaches and notify the regulator and affected people when serious harm is likely; see website security for Australian small businesses for the incident sequence.

12

Backend, Backups and Recovery

The app on the device is only half the system. Maintain the backend as well: patch servers and runtimes, rotate secrets, monitor API error rates and latency, and back up databases and uploaded files. Test backups by restoring them; a backup that has never been restored is an assumption. Agree recovery objectives: how much data the business can afford to lose and how long the service can be down.

13

What to Put in a Maintenance Agreement

Whether maintenance is done by an internal team or a partner, write it down. A useful agreement covers:

ItemWhat to agree
ScopeWhat is maintenance (fixes, OS and store updates, dependency and security updates) and what is a new feature
Severity levelsDefinitions, for example critical, high, normal, low
Response and resolution timesPer severity, during and outside support hours
Support hours and time zoneWhen the team is reachable, and how out-of-hours emergencies are handled and charged
Release processTesting, staged rollout, rollback and who approves releases
Monitoring and reportingWhich dashboards are watched and how often you receive a summary
SecurityPatching timeframes for critical vulnerabilities; incident cooperation
OwnershipCode, signing keys, store accounts and cloud accounts belong to the business
Pricing modelRetainer, hours bank or per request, and how unused hours are treated
ExitHandover documentation and transition support if the agreement ends
14

Planning the Maintenance Budget

There is no reliable percentage that fits every app. The '15 to 20% of build cost a year' figure repeated across the web has no published method behind it, so we do not use it. Budget from the worksheet instead: for each of the eleven rows, note how many of the 'what makes it bigger' drivers apply to your app, then ask for an estimate against that list. Add the fixed platform fees, hosting and third-party services, monitoring tools, support hours and a bug-fix allowance. Apps with many integrations, many SDKs, native modules or sensitive data need more.

Ask for a maintenance estimate before signing the build contract, so the long-term cost is part of the decision. The guide to what drives mobile app development cost explains how build decisions carry into running costs. If you want a team to own this work, ZSpace Labs offers mobile app development and post-launch support.

Australian businesses can find a lifecycle budget model, GST and store fee considerations in mobile app development cost in Australia, and support-hour and contract questions in choosing a mobile app development company in Australia.

15

Hypothetical example: a booking app one year after launch

Hypothetical example: a two-sided booking app built in React Native, with a payments SDK, an analytics SDK, push notifications and a small backend. Running the worksheet, the founder finds three rows that need the most attention. Row 3: the app shipped on a React Native version that has since dropped to End of Cycle, so an upgrade is due before it becomes unsupported. Row 4: the analytics SDK was upgraded in a hotfix without anyone checking the Data safety form. Row 6: the Apple Developer account was opened by the original contractor, who is still the Account Holder.

The founder moves the Account Holder role into the business first, because a missed renewal would remove the app from every storefront. Then the team schedules the framework upgrade ahead of Apple's late-April window and Google's August deadline, so one toolchain upgrade covers both. The example is illustrative and does not describe a real client.

16

When This Plan Does Not Fit

The worksheet assumes an app you intend to keep growing. If the app is a short-lived campaign or a prototype you plan to retire, a lighter plan is reasonable: keep the accounts renewed and the store listing compliant until you remove it, and skip the improvement cycle. If the app is in a regulated sector such as health or finance, the worksheet is a starting point only; your regulator's requirements for security testing, records and incident reporting come first. And if most of the work is now fighting an old codebase, maintenance may not be enough; see mobile app modernisation.

17

Maintenance Checklist

  • Crash and performance dashboards reviewed after every release
  • App tested against each new iOS and Android version
  • Store target API and SDK requirements tracked
  • Apple Account Holder and Play Console owner are people in the business
  • Dependencies and SDKs updated on a regular cadence
  • Privacy manifests, App Privacy details and Data safety form checked whenever an SDK changes
  • Security patches applied promptly
  • Store deadlines (Xcode/SDK minimums, Android target API level, membership renewal) in the calendar
  • Staged rollouts, feature flags and a hotfix path ready
  • Backend patched, backups restored in a test, secrets rotated
  • Older app versions monitored and a minimum version policy defined
  • Analytics reviewed and improvements prioritised
  • Documentation and ownership kept current
18

Conclusion and Next Steps

An app is a living product on platforms that keep changing. Maintenance keeps it working, secure, compliant and improving. This week, copy the worksheet, name an owner for each row, and put the calendar dates in a shared diary, starting with your Apple membership renewal. Then check your framework version against React Native's support table and your SDK list against your privacy declarations.

For how this fits the whole build, see the mobile app development guide. For the contract terms behind a maintenance plan in Australia, see software maintenance contracts.

Want a maintenance plan built around your app?

ZSpace Labs is a remote-first technology studio that works with clients globally on mobile app development. If useful, we can talk through a maintenance plan based on your app's SDKs, framework version and platform deadlines.

Start a Project
19

Sources

Apple: Upcoming requirements; Apple Developer: resolving access issues (membership expiry); Third-party SDK requirements.

Google: Target API level requirements for Google Play apps (updated 1 October 2026); Android vitals; Android developer verification; Google Play policy announcements; Google Play Help: Data safety section.

Frameworks: React Native: releases overview; React Native: versioning policy; Flutter: compatibility policy.

Accessed 15 October 2026. Platform deadlines, policies and support windows change; check the source pages before planning around a date.

FAQ

Common questions.

Operating systems, devices, store policies, dependencies and APIs change constantly. Without updates, apps break, fall out of store compliance, become insecure and lose users.

Bug fixes, OS and dependency updates, security patches, performance and crash monitoring, analytics review, API changes, store requirement updates and feature improvements.

There's no fixed rule, but most active apps release updates regularly, and every app needs updates when major iOS or Android versions ship or store requirements change.

It can crash on new OS versions, accumulate security vulnerabilities and decline in ratings. On Google Play, an existing app must target Android 15 (API level 35) or higher to stay available to new users on devices running a newer Android version; an app targeting API 34 or lower is only available on devices running its target version or lower. New apps and updates need API 36 from 31 August 2026, so an unmaintained app also cannot ship a fix until it is upgraded.

Tools that collect details about crashes in production, including device, OS and stack traces, so developers can find and fix causes quickly.

Google Play requires apps to target a recent Android API level, and Apple periodically raises minimum Xcode and SDK versions for submissions. Meeting these requires ongoing work.

An internal team, the original development partner or a dedicated provider. What matters is that ownership is explicit and the code is documented.

By work type rather than by a percentage of the build cost. List the recurring work in the worksheet above, note what makes each item bigger for your app (native modules, the number of SDKs, regulated data, release frequency) and ask for an estimate against that list. The common 'percentage of build cost' rule has no published method behind it.

Scope (what counts as maintenance versus new features), response and resolution times by severity, support hours and time zone, how releases and hotfixes are handled, who owns accounts and code, monitoring and reporting, a security patching commitment, the pricing model (retainer, hours bank or per request) and exit and handover terms.

A good process confirms impact from monitoring, decides whether to pause a staged rollout, fixes and tests a hotfix, submits it with an expedited review request if needed, and communicates with affected users. Server-side feature flags help by letting teams switch off a broken feature without waiting for a new app release.

Apple says apps and In-App Purchases become unavailable in all storefronts, although apps already on customers' devices stay installed. You also lose access to TestFlight, Certificates, Identifiers & Profiles, the App Store Connect API and Xcode Cloud. Only the Account Holder can renew, so make sure that person is someone in your business.

Mostly through Play Console. Google says Play automatically registers 99% of apps; the rest, and apps distributed outside Google Play, are registered manually. Protections began on 30 September 2026 for installs from participating stores in Brazil, Indonesia, Singapore and Thailand, with a global rollout planned for 2027.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.