The Ultimate Guide: Moving From Closed Testing to Production

The waiting is over. You survived the brutal 14-day continuous testing streak without dropping below the minimum tester threshold. You managed to avoid the lethal mistakes that lead to an automatic rejection. The Google Play Console finally shows that beautiful, green "Apply for Production" button.

But the journey isn't quite finished. Moving an app from a closed testing track to the global public store involves more than just clicking a button. You need to handle version codes, manage your production release rollout percentage, and ensure your final App Bundle is polished.

In this comprehensive playbook, we are going to walk you through exactly what happens after day 14, how to promote your release, and how to safely navigate your first public launch.

Phase 1: Passing the Final Review

Before you can actually touch the Production track, you have to pass the manual human review. Clicking "Apply for Production" opens up a detailed questionnaire.

This is Google’s final check to ensure you actually used the testing period properly. You will need to detail exactly how you gathered testers, what specific feedback they gave you (bugs, UI issues, feature requests), and what changes you made in response. If you just type "It works good," you will be rejected. Be sure to use our proven questionnaire answer templates to guarantee you pass this stage.

Once submitted, your account enters a "Pending Review" status. This can take anywhere from 1 to 7 days. Crucial rule: Do not stop your closed test during this period. Keep your testers engaged until you receive the final approval email.

Phase 2: Preparing Your Final App Bundle

Once you get the email stating "Production Access Granted," it is time to prep your final code. The .aab (Android App Bundle) you used for testing might be fine, but a proper production launch usually requires a fresh build.

Here is your pre-flight checklist for the final code:

• Increment your Version Code: If your last closed testing build was `versionCode 5`, your production build must be at least `versionCode 6`. The Play Console will throw an error if you try to upload a duplicate version code.
• Remove Debug Logs: Ensure all console logging, strict mode penalties, and debug-only tools (like LeakCanary) are stripped from your release build.
• Switch to Production APIs: If you were pointing to a staging server or a sandbox database during the test, update your base URLs to point to your live production backend.
• Update the Version Name: Change your user-facing version name from "1.0.0-beta" to a clean "1.0.0".

Phase 3: Promoting to Production (Step-by-Step)

You do not actually have to upload the file to a brand new screen. Google Play allows you to "promote" an existing release.

1. Log into your Google Play Console and select your app.
2. Navigate to Testing > Closed testing on the left menu.
3. Find the release you want to publish (the one that passed the 14-day test).
4. On the right side of that release, click the Promote release button.
5. Select Production from the drop-down menu.

This action creates a draft in your Production track. If you built a brand new .aab (as recommended above), you can discard the old testing bundle on this screen and upload your fresh `versionCode 6` bundle.

Phase 4: The Staged Rollout Strategy

When you get to the bottom of the Production release screen, you will see an option for Rollout Percentage. It defaults to 100%. If you are a solo developer launching your first app, do not launch at 100%.

A 100% rollout means the app is instantly available to anyone globally who clicks download, and if your app crashes for a specific hardware subset, your store rating will instantly tank to 1 star. Instead, use a Staged Rollout.

Recommended Rollout Plan:

• Day 1: 10% Rollout. This allows a small fraction of organic users to find your app. Monitor your Android Vitals dashboard closely for the next 24 hours. Look for new ANRs (App Not Responding) or Crashlytics reports.
• Day 3: 50% Rollout. If your crash rate remains below the 1.09% threshold, increase the percentage. You can do this by going back to the Production track and clicking "Update rollout."
• Day 5: 100% Rollout. If the servers are stable and users aren't reporting critical bugs, open the floodgates.

If you discover a critical bug at the 10% phase, you can simply halt the rollout, fix the bug in Android Studio, and push a new update. The 90% of users who haven't seen the app yet will be spared the bad experience.

Phase 5: Post-Launch Housekeeping

Once you hit 100% rollout, you are officially live. But your job isn't done. The first 30 days are critical for the algorithm to determine your app's ranking.

• Reply to Every Review: Google's algorithm favors developers who are active. Reply to all reviews, especially the negative ones, politely explaining that you are working on fixes.
• Update Your Store Listing: Remove any mention of "Beta" or "Early Access" from your app description and promotional screenshots.
• Monitor Vitals: Google will restrict your app's visibility on the store if your crash rate exceeds the "bad behavior threshold" (usually 1.09% for crashes and 0.47% for ANRs). Keep those numbers low.

The Prerequisite to Launching

All of this advice is useless if you are still stuck at Day 3 of your closed testing phase because your friends keep deleting your app. You cannot access the production track until you fully satisfy Google's strict tester requirements.

If you are struggling to find real Android testers, or if you are terrified of using bot farms that might ban your account, 12 Testers Hub is the solution.

We provide a network of real users, with real devices, who will fulfill your 14-day continuous requirement. We generate the engagement data you need to confidently answer the final questionnaire and secure your production access. Stop waiting on unreliable testers and let us push you to the finish line today.