Android Play First Release

Use this for a first Android release when the Play developer account already exists.

Checklist

1. Reserve the package identity.
2. Build a release Android App Bundle (.aab).
3. Enroll or confirm Play App Signing.
4. Protect the upload key outside the repo.
5. Complete app content, target audience, privacy policy, and Data safety.
6. Upload to internal testing first.
7. Install from Play on a real test device.
8. Fix pre-launch report, crash, ANR, permission, or policy issues.
9. Prepare listing assets from the release build.
10. Move through closed/open testing only if the app or account requirements need it.
11. Submit production release when the release gate passes.
12. Monitor Android vitals, reviews, crash rate, and ANR rate after launch.

Build and Signing Model

For Play distribution, publish an Android App Bundle. You sign the AAB with the upload key, then Play App Signing signs optimized APKs for users.

Do not make the upload key a developer laptop snowflake. Store it in a secret manager or CI signing path and document recovery.

Data Safety First Pass

Create a table before opening the Play form:

Then map the table into Play Data safety. If the app collects no data, still complete the form and provide the required privacy policy when applicable.

Listing Assets

Prepare at minimum:

• App icon.
• Short description.
• Full description.
• Feature graphic.
• Phone screenshots.
• Tablet screenshots if tablets are supported.
• Privacy policy URL.
• Support contact.

Gotcha: Screenshots must match what users actually get. Do not use mockups that show unreleased features, impossible states, or misleading AI claims.

Release Track Flow

flowchart TD
    aab[Signed AAB] --> internal[Internal testing]
    internal --> device[Install from Play on test device]
    device --> checks{Release gates pass}
    checks -->|No| fix[Fix build, policy, assets, or data safety]
    fix --> aab
    checks -->|Yes| review[Production review]
    review --> production[Production release]
    production --> vitals[Monitor vitals and reviews]

For updates, use staged rollout when risk is non-trivial. Start small, watch crashes and feedback, then increase percentage manually.

Account-Type Caveat

Google has additional testing requirements for some personal developer accounts created after November 13, 2023. The lab owner already has a Play developer account, but this topic does not verify account type or age because it does not access authenticated dashboards.