How to Publish an Android App on Google Play

Your app works on your phone. Getting it onto Google Play involves a developer account, a signed release, a testing period, a store listing and several policy declarations. None of it is hard, but each step has details that can delay you by days if you miss them.

The path to production

1. Create a developer account

• Register in the Play Console. There's a one-time registration fee.
• Choose personal or organisation account. Organisations need verification details such as a D-U-N-S number.
• Complete identity verification and contact-detail verification.

2. Prepare a signed release

1. Set a unique applicationId, which is permanent, plus versionCode and versionName.
2. Target the required API level, and test behaviour changes for that Android version.
3. Enable R8 and resource shrinking, and test the minified build. See Prepare for Production.
4. Generate an upload key and enrol in Play App Signing. See App Signing.
5. Build an Android App Bundle: ./gradlew bundleRelease.

3. Store listing and policy forms

4. Testing tracks

• Internal testing: up to a limited number of testers, available within minutes. Use it for quick team checks.
• Closed testing: invited testers (email lists or Google Groups). New personal developer accounts must run a closed test that meets Google's minimum tester count and duration before they can apply for production. Commonly cited requirements are 12 opted-in testers for 14 consecutive days. Check the current numbers in Play Console Help.
• Open testing: public beta on your store listing.

5. Release to production

1. Apply for production access (for new personal accounts) after meeting testing requirements, answering questions about your testing.
2. Create a production release, upload the AAB, and write release notes.
3. Use a staged rollout (for example 10% → 50% → 100%) and watch crashes and ANRs in Android vitals.
4. Review can take from hours to several days, longer for new accounts or sensitive permissions.

Situations

Common reasons for rejection or delays

• Data safety form doesn't match the app or SDK behaviour.
• Missing or inaccessible privacy policy, or no test credentials for login-gated apps.
• Restricted permissions without justification (SMS, call log, background location).
• Misleading metadata or impersonation in the listing.
• Target API level below the requirement.

Frequently asked questions

Conclusion

Publishing on Google Play means a verified account, a signed App Bundle targeting the required API level, a complete listing and policy forms, a genuine closed test (for new personal accounts), and a staged production rollout. Start the slow steps early.

Next step: get signing right once and for all in Android App Signing and Upload Keys Explained.