How to publish an Android app on Google Play for the first time

Short answer: create and verify your Play Console account, upload a signed Android App Bundle, complete the store and policy declarations, publish a closed test, keep at least 12 testers opted in continuously for 14 days if the rule applies to your account, apply for production access, and then release to production.

1. Check whether the 12-tester rule applies to your account

Google applies the closed-testing gate to personal developer accounts created after 13 November 2023. Those accounts must have at least 12 testers opted in continuously for the preceding 14 days before applying for production access. Organisation accounts and older personal accounts are not in that specific gate, although testing before release is still sensible.

2. Prepare the app and Play Store listing

Upload a signed .aab file, not an APK intended for direct distribution. Complete the app name, short and full descriptions, icon, screenshots, category and contact details. Then finish the App content sections that apply to you: privacy policy, ads declaration, content rating, target audience, data safety and any permissions declarations.

Do not treat policy review as a debugging service. Your app and listing need to comply before you submit them.

3. Use internal testing for a quick technical check

Internal testing is optional and does not satisfy the 12-tester requirement. It is still the fastest way to confirm that the correct bundle installs, sign-in works and the main flow does not crash. Fix obvious failures here before asking a wider group to test.

4. Create and publish a closed-testing release

In Play Console, open Test and release → Testing → Closed testing. Add testers by email list or Google Group, create a release, upload the bundle, and roll it out. A saved draft is not available to testers. The release must reach a published testing state before the opt-in link works.

5. Get testers to opt in correctly

Adding an email address is only the invitation step. Each tester must use an eligible Google account, open the opt-in link, accept the test and install the Play Store build. If you use a Google Group, the tester must join the group before opening the opt-in link.

Start with more than 12 people. The requirement is continuous, so a buffer protects the schedule if someone leaves.

6. Use the 14 days as an actual test

Keep the track active and collect specific feedback. Google’s production-access form asks how testers used the app, what feedback they gave, what you changed and why you consider the app ready. A list of real observations is more useful than a generic claim that everything worked.

7. Apply for production access

When Play Console recognises the completed window, the Dashboard enables Apply for production. Answer the three sections about your closed test, your app and production readiness. Google reviews that application and emails the account owner when it finishes.

8. Create the production release

Production access is permission to publish; it does not always mean the app is already public. Promote the tested release or create a production release, choose countries and rollout settings, review the changes, and submit. Google notes that some account reviews can take up to seven days or longer in exceptional cases.

Where to go next

• Set up the closed track step by step
• Find 12 testers without paying
• Prepare the production-access application

Official sources

Google Play: testing requirements for new personal accounts · Google Play: set up a test · Google Play: publish your app