In this guide
Finishing the closed test is not the finish line. Two steps remain: Google approves your production access, then you release. This page covers what comes after the approval.
Step 1: apply and wait for the decision
When your closed test meets the criteria, the Play Console Dashboard offers "Apply for production". The form asks about your closed test, your app and your production readiness. Google then reviews it; the help page says this "usually takes seven days or less" and that the account owner gets an email when the review finishes.
If approved, you can open the Production page and distribute your app. Open testing becomes available too.
Step 2: create the production release
Do not just push the last test build. Before you release:
- Compare the build with the one your testers used. Everything you changed since then is untested.
- Re-read the feedback you collected and confirm that the issues you marked as "must fix" are fixed.
- Check store listing, privacy information and app content declarations in Play Console.
- Write release notes for real users, not for testers.
Step 3: staged rollout, with a catch
A staged rollout sends the release to a percentage of users first. Per Google's help page: you choose the percentage when you roll out, it "won't increase automatically", and you can halt it; users who already received the version stay on it.
The catch: the same page says staged rollouts "can only be used for app updates, not when publishing an app for the first time." So your very first production release goes to everyone who can see it. Plan accordingly: this is exactly why a thorough closed test matters. For later updates, use a staged rollout and read how to test an update to a live app.
Rollout checklist
- Release build matches the tested build, plus only known fixes.
- Crash reporting is switched on before the release.
- Release notes written.
- You have time in the next days to watch reviews and crashes.
- For updates: start with a small percentage, check, then increase manually.
- Know your rollback plan: halt the rollout, fix, release a new version.
Keep testing after launch
Testers who helped in the closed test are your best source for the next update. Keep a small group and let them check each release before you widen the rollout.
AppReviewX offers test groups for Google Play closed testing (12 testers, 14 continuous days, for Android apps) and private structured feedback. Store reviews on AppReviewX are voluntary and unpaid. Join a test group.
Related: Google Play closed testing: the complete guide, Closed test calendar, Tester email list formatter.