From Upload to Production: Android App Release Explained

Shipping on Google Play is a sequence: create the app, upload builds, test, then unlock production. For many indie developers, closed testing is the longest gate.

The Release Journey

1. Build and prepare — Signed App Bundle, store listing assets, policy-ready content.
2. Play Console setup — Create the app, complete required declarations.
3. Closed testing — Upload to a closed track, add testers, run the required window if you are in scope.
4. Apply for production access — For personal accounts created after November 13, 2023, after 12 testers opted in continuously for 14 consecutive days with real use (minimum is 12 now, not 20). Organization / D-U-N-S accounts are generally exempt from that personal-account rule.
5. Production — Once approved, promote/release to production and maintain the app.

Detailed Steps

Uploading your app

Create the application in Play Console, complete the listing, upload a signed AAB to the appropriate track, and submit the release for review as prompted.

Closed testing phase

1. Open Release > Testing > Closed testing
2. Create/manage the track and upload the build
3. Add testers (email list and/or Google Group)
4. Share the opt-in link; fix item-not-found / opt-in 404 issues (account, country, group sync)
5. Keep 12+ continuous opted-in testers engaging for 14 consecutive days if you are under the personal-account rule

Applying for production

When Play Console shows you can apply, use the Dashboard flow, answer testing and readiness questions, and submit. Google reviews policy compliance and testing signals.

Common Delays

• Closed test: under 12 testers, broken continuity, weak engagement, install/access failures
• Review: policy, metadata, or “continue closed testing” feedback

Tips for Success

Finish the product enough for daily use, recruit a buffer of testers, monitor every day, and use reminders. Closed Test Pro helps specifically at the closed testing stage—community testers, tracking, and automated reminders—so the upload-to-production path does not stall for two weeks on flaky participation.

Master closed testing, and the jump from upload to production becomes a review step instead of a reset loop.