The short answer
- You cannot roll back a mobile app that people have installed, so safe releases depend on staged rollouts, feature flags and an API that supports older versions.
- The App Store’s phased release spreads automatic updates over seven days, and Google Play’s staged rollout lets you choose the percentage and halt it.
- A minimum supported version, checked by the app when it starts, lets you require an update when an old version can no longer work safely.
To release mobile app updates safely, roll each version out gradually with the stores’ staged release tools, hide risky changes behind feature flags, keep your API compatible with older app versions, and watch crash reports before widening the rollout. A staged rollout is a release that reaches a growing share of users over several days, so a problem affects a few people before it affects everyone. All of this matters because an app that is already on someone’s phone cannot be taken back.
Why mobile releases are different from the web
When a web release goes wrong, you deploy the previous version and every user has it within minutes. Mobile apps do not work that way. Each version is reviewed by the store, downloaded to each phone and updated when the person or their phone decides. At any moment your users are running several versions, some of them months old, and some people turn automatic updates off entirely.
Three principles follow. Limit how many people get a new version until you trust it. Control new behaviour from the server, where you can change it instantly. Keep the server working for every version still in use.
Version numbers and build numbers
Both platforms use two numbers. The version is what people see in the store, such as 2.4.1. The build number is an internal counter that must go up with every build you upload. On iOS these are the version string and the build number, and on Android they are versionName and versionCode, where versionCode is a whole number that must be higher for every release you upload to Google Play.
Most teams use semantic versioning for the visible number, with major, minor and patch parts. Raise the patch number for fixes, the minor number for new features and the major number for large changes. Keep the version the same on iPhone and Android for the same release, so support conversations are not confusing.
Staged rollouts on the App Store and Google Play
Both stores let you release to a share of users first. They work differently, and neither lets you take a version back.
| App Store phased release | Google Play staged rollout | |
|---|---|---|
| How it works | Automatic updates reach a growing share of existing users over seven days | A percentage of users you choose is offered the update, and you raise it when ready |
| Schedule | Fixed at 1%, 2%, 5%, 10%, 20%, 50%, then 100% | Any percentage, at any pace |
| Pausing | Can be paused for up to 30 days in total, or released to everyone at once | Can be halted, then resumed or replaced by a new release |
| Who gets it early | New downloads, and anyone who updates manually from the store | A random selection of users, up to the percentage you set |
| Going back | Not possible; ship a new version with the fix | Not possible; halting stops more people getting it, and a fix needs a new release with a higher versionCode |
Use the time the rollout gives you. Watch crash reports, server error rates and support messages at each step, and agree in advance what would make you pause. On Google Play, a common pattern is to start small, wait a day or two, then widen. Apple offers expedited review for urgent fixes, but it is not guaranteed, so keep it out of the plan. The first submission has its own hurdles, covered in passing app review first time.
Feature flags and kill switches
A feature flag is a setting, held on your server or in a remote configuration service, that turns a piece of functionality on or off without a new release. It separates shipping code from switching it on. A new feature can go out in a release switched off, be turned on for staff, then for a small group of customers, then for everyone. If something goes wrong, it is switched off in seconds for every version that contains the flag.
A kill switch is a flag for something that already works, such as a payment method or a third-party integration, so it can be turned off if a provider has an outage. Keep flags tidy. Remove each one once a feature is fully live, or the code fills with branches nobody remembers.
Forced updates and minimum versions
Sometimes an old version has to stop working, because it has a security flaw or depends on an API you need to retire. Neither store forces updates on your behalf, so the app has to do it.
- When the app starts, it asks your server for the minimum supported version and, optionally, a recommended version.
- If the installed version is below the minimum, the app shows a screen that explains why, links to the store and does nothing else.
- If it is below the recommended version, the app shows a prompt that can be dismissed.
- On Android, Google Play’s in-app updates API can download and install the update from inside the app, either straight away or in the background while the person carries on.
Build the check into the first release, because a version that shipped without one can never be made to show it. Use forced updates rarely, since they interrupt people at a moment they did not choose, and test that the update screen itself works on the oldest supported version.
Keeping the API working for old versions
Every version still in use is a client of your API. A change that is safe for the latest app can break one that is three months old.
- Make changes additive. Add new fields and endpoints, and leave the old ones in place.
- Never change the meaning of an existing field. Add a new one instead.
- Remove something only after the minimum supported version no longer uses it.
- Change the database in two steps, often called expand and contract. Add the new structure, move data and clients across, and remove the old structure in a later release.
- Have the app send its version with each request, so the server can tell which versions are still active.
Offline-first apps need extra care. Estimark saves to the phone first and syncs later, and an app built that way can reconnect after days with changes queued by an older version. The server has to accept those changes, and each new version has to migrate the database on the phone without losing anything that has not yet synced. Our guide to offline-first mobile apps covers the sync side.
Crash monitoring and release checks
Crash reporting tools, such as Firebase Crashlytics or Sentry, capture each crash with the device, operating system and app version. Apple’s Xcode Organizer and Google Play’s Android vitals report crashes and freezes too. Google Play publishes thresholds for crash and “app not responding” rates, and apps above them may be shown less prominently in the store.
Compare the crash-free rate of the new version with the previous one at each stage of the rollout. A short checklist keeps releases routine.
- Test the release build on real devices, including the oldest supported operating system.
- Upgrade from the previous version with real data on the device, as well as testing fresh installs.
- Confirm that new features are behind flags and switched off.
- Confirm that the API changes are already live and work with the previous app version.
- Release to a small percentage and watch crashes, errors and support messages.
- Widen the rollout in steps, then switch features on gradually.
Each release also adds to the yearly cost of running an app, which is covered in software maintenance costs.
Questions people ask
Can I roll back an app update on the App Store or Google Play?
No. Neither store lets you restore a previous version for people who have already updated. To undo a bad release, you ship a new version, often built from the previous code, with a higher build number. Feature flags and staged rollouts reduce how often you need to.
How long does Apple’s phased release take?
Seven days, if it is not paused. Automatic updates reach 1%, 2%, 5%, 10%, 20% and 50% of existing users on successive days, then everyone on day seven. You can pause it for up to 30 days in total, or release to everyone at any point.
How do I force users to update my app?
Build a minimum version check into the app. When it starts, it asks your server which versions are still supported and shows an update screen if the installed version is too old. On Android, Google Play’s in-app updates API can run the update from inside the app.
What is a feature flag?
A feature flag is a setting controlled from your server that turns a feature on or off without releasing a new version. It lets you ship code switched off, turn it on for a small group first and switch it off instantly if something goes wrong.