Short answer: upload a build to the internal track, promote that same build through closed and open testing, then start production at a small percentage of users. Watch crashes and reviews, raise the percentage in steps, and halt the rollout if something goes wrong. You fix a bad release by shipping a new build with a higher version code, not by rolling back.
The four tracks
Google Play has three testing tracks and production:
| Track | Who gets the build | Typical use |
|---|---|---|
| Internal testing | Up to 100 testers you list | Every build, for the team |
| Closed testing | Testers you invite by email list or group | Beta with known users |
| Open testing | Anyone who joins from the store listing | Public beta |
| Production | Everyone, or a percentage of them | The release |
You upload an app bundle once. After that you promote the same build from track to track, so what reaches production is byte for byte what your testers used.
If your developer account is a personal account created after 13 November 2023, Google requires a closed test with at least 12 testers opted in for 14 days in a row before you can apply for production access.
What a staged rollout does
When you promote to production you choose what share of users receive the update, for example 5%. Play picks those users at random. New installs of your app from that group get the new version; everyone else keeps the current one.
A sensible ladder looks like this:
- 5% for a day. Enough users to surface a crash that testing missed.
- 20% for a day or two. Watch the crash rate, ANR rate and new one-star reviews.
- 50%, then 100%.
How long to wait at each step depends on how many users you have. A small app may need several days at 20% before the numbers mean anything.
Halting a rollout
If the new version is crashing, halt the rollout in Play Console. Users who have not received the update stay on the old version. Users who already have it keep it: halting does not remove a version from anyone's phone.
That is the part people get wrong, so plainly: Google Play has no rollback. A device will not install a build with a lower version code than the one it has. To fix a bad release you upload a new build with a higher version code, usually the previous code with the fix or the previous code unchanged, and roll that out.
Before you start a rollout
- Check Android vitals for the build in testing: crash rate and ANR rate.
- Make sure release notes are within Play's 500-character limit for each language.
- If you use managed publishing, remember an approved change does not go live until you publish it.
- Decide who is allowed to press the production button. A second pair of eyes is cheap.
Doing it without Play Console
Everything above is available through the Google Play Developer API: uploading a bundle, promoting between tracks, setting the rollout fraction and halting. That is how release tools work.
VenelX Studio calls that API from your own Mac. The Releases screen shows each track with the build on it, promotes with one click, offers 5%, 20%, 50% and 100% rollout steps, and can require a teammate's approval before production. The Play service account stays in the Mac's Keychain and is never uploaded to VenelX servers.