How to Update an App on Google Play (New Version)
The full release routine for new versions: version codes, signed bundles, release notes, tests and a safe rollout.
Read the guide →Google Play Staged Rollout Explained: When to Use It
Quick answer A Google Play staged rollout sends an update to a percentage of users, which you raise yourself. You can halt or resume it, but halting does not roll anyone back. It works for updates only.
Every developer has shipped an update and then watched the one-star reviews arrive. A staged rollout is the safety net Google Play gives you: instead of sending your new version to everyone at once, you send it to a small percentage and widen the circle only when it looks healthy. This guide explains Google Play staged rollout in plain language: how it works, how to start, increase, halt and resume it, and a simple plan you can reuse for every update.
What is a staged rollout on Google Play?
A staged rollout lets you release an update to a percentage of your users, then increase that percentage over time. Google's staged rollout help page describes it as your update reaching only a percentage of your users, chosen at random for each new rollout. The idea is simple: if the update has a hidden bug, only a few users meet it, and you can stop before it spreads.
How does it work?
| Question | Answer from Google's page |
|---|---|
| Who gets the update | A random percentage of eligible users |
| Does the percentage grow automatically | No. You update it yourself. |
| Can it be used for a first release | No. Updates only. |
| Do users know | No notification when they receive a staged version |
| Can you limit it by country | Yes, and you cannot remove countries after it starts |
| What if another release starts during a rollout | It uses the same user group as the previous release, depending on the percentage |
How do you start a staged rollout?
- Prepare the releaseBuild and test your bundle as in how to update an app.
- Open the production trackCreate a new release and upload the bundle.
- Find the rollout sectionIn the release, set a percentage in the Staged rollout section.
- Choose countries (optional)You can limit the rollout to specific countries or regions.
- Start the rolloutClick Start rollout to production.
Country availability is set when you update a production release. Remember that once the rollout has started you cannot remove any countries.
How do you increase, halt and resume a rollout?
| Action | How | Effect |
|---|---|---|
| Increase | Releases tab > Manage rollout > Update rollout, enter a new percentage, Confirm update | More users receive the version |
| Halt | Manage rollout > Halt rollout | No new users receive it. Existing users keep it. |
| Resume | Manage rollout > Resume rollout, set the percentage, confirm | Rollout continues for the same users as before |
| Finish | Increase the percentage to 100% | Everyone eligible can receive the update |
Google recommends updating your store listing only after the release has reached 100% of users, so the listing does not describe features that some users do not have yet.
What is a safe rollout plan?
Google does not prescribe percentages, so this is a practical suggestion. Adjust it to your user base: tiny apps may need higher starting percentages to get meaningful data.
| Stage | Percentage | Wait before moving on | Check |
|---|---|---|---|
| 1 | 1% to 5% | 1 to 2 days | Crashes, ANRs, login issues |
| 2 | 10% to 20% | 1 to 2 days | Reviews, support emails |
| 3 | 50% | 1 to 2 days | Performance, purchase flow |
| 4 | 100% | - | Update store listing and notes |
What should you watch during a rollout?
- Crash and ANR rates in the stability reports of Play Console.
- New reviews mentioning the version.
- Support email and social mentions.
- Key actions in your analytics, such as sign-ups and purchases.
- Device or country patterns: a bug that only affects one phone model is easy to miss at 100%.
If something looks wrong, halt first, investigate second.
What are the limits of staged rollouts?
- They are for updates only. Your first release goes to its audience without staging, which is one more reason to test thoroughly in a closed track. See closed testing vs open testing.
- Halting is not a rollback. Google's page describes no way to revert users to an earlier version.
- To fix a bad release, create and roll out a new release with a fixed bundle and a higher versionCode.
- A staged rollout cannot fix policy issues. For that see app rejection reasons
- Full rollout may take time even at 100%.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: Release app updates with staged rollouts
- Android Developers: Version your app
How does a staged rollout play out in real life?
These are illustrative scenarios, not Google rules. They show how the same tool supports different decisions.
| Scenario | What you see | What to do |
|---|---|---|
| A small bug only some phones hit | Crashes appear on one device model at 5% | Halt, fix, release a new version with a higher versionCode, then restart at a small percentage |
| Everything looks healthy | Crash rate unchanged, reviews normal | Increase in steps until 100% |
| A new payment flow | Sales dip at 20% | Halt, check the flow, test again in an internal track |
| A policy change due soon | You need everyone on the new version | Increase faster, but still watch the first 24 hours |
Pre-rollout checklist
| Check | Done? |
|---|---|
| versionCode is higher than the live version | ☐ |
| Signed with the right upload key. See app signing explained | ☐ |
| Tested as an update on top of the previous version | ☐ |
| Content rating, Data safety and target audience still accurate. See the questionnaire guide | ☐ |
| Release notes written | ☐ |
| Store listing changes saved for after 100% | ☐ |
Staged rollout vs testing tracks
A staged rollout is not a substitute for testing. It limits the damage of a bug, but those users still meet the bug. Use internal and closed testing to catch problems first, and the rollout to catch what testing missed. Your very first release cannot be staged, so a thorough closed test matters even more; see the closed testing requirements.
Frequently asked questions
Can I use a staged rollout for my first release?
No. Google says staged rollouts apply to updates only, not to first-time publishing.
Does the percentage increase by itself?
No. Google says the percentage does not rise automatically. You update it yourself.
What does halting a rollout do?
No new users receive the version. Users who already have it stay on it.
Are users told they are in a staged rollout?
No. Google says users are not notified when they receive a version through a staged rollout.
Can I remove a country after the rollout starts?
No. Google says you cannot remove countries once the rollout starts.
Is halting the same as rolling back?
No. Google's page describes halting, not reverting to an earlier version. To fix a bad release, create and roll out a new release with a fixed app bundle.
