Publishing an app on Google Play costs $25 once, with no annual subscription. Yet it is the journey that surprises people the most: since late 2023, a personal developer account can no longer push an app straight to production. It must first run the app in closed testing with 12 testers for 14 consecutive days, then apply for production access. Many first launches stall on this rule, not on the technology.
The rest of the path is well tooled: the app bundle format, signing handled by Play App Signing, and progressive testing tracks that deliver a build to your testers in minutes, with no review. This guide follows the real order of operations, with the rules in force in 2026.
It covers Android only. iOS is a different path with its own dedicated guide: publish an app on the App Store. To compare both stores, our App Store and Google Play checklist puts the two journeys side by side.
The developer account and the 2026 rules
The account is created in Play Console, with a one-off $25 fee and an identity check that can take a few days. The choice between a personal and an organization account matters more than it looks:
| Personal account | Organization account | |
|---|---|---|
| Production access | After a closed test with 12 testers for 14 days (accounts created after 13 November 2023) | Direct, no tester requirement |
| Verification | Identity document | DUNS number and company checks |
| Publisher name shown | Your name | The company name |
Testing tracks and production access
Google Play is built around four tracks, from the most private to the most public. Each release climbs from one track to the next, and Google's review only happens at the production step.
- Internal testing: up to 100 testers by email list, release available in minutes, no review. This is the everyday working track.
- Closed testing: a larger invited group, with a real install journey from the store. This is where the 12-tester requirement plays out.
- Open testing: anyone with the link can join and the listing becomes visible. Optional, useful for a public beta.
- Production: all users, with Google's review on the way in and staged rollout available.
The 12-tester gate
For a personal account created after 13 November 2023, Google requires a closed test with at least 12 opted-in testers for 14 consecutive days before opening production access. Opted-in means the tester accepted the invitation and installed the app under the matching Google account: an invitation without an install does not count. The threshold started at 20 testers and was lowered to 12 on 11 December 2024. The exact conditions are described in the official Google Play documentation.
Once the 14 days have passed, you fill in a short application about your app and your testing, and Google usually answers within 7 days. Recruit early: family, colleagues, developer communities that exchange testing slots. The clock only runs while 12 installs are active at the same time.
Step by step, from build to production
- Create the developer account. $25 once, identity verification, then access to Play Console to manage apps, testers and releases.
- Produce a signed app bundle. The expected format is the AAB, signed with an upload key. With Play App Signing, Google holds the final signing key: if your upload key is lost, it can be reset without losing the app.
- Create the app in Play Console. Display name and package name. The package name is permanent: it identifies your app forever.
- Publish a release to internal testing. Add your testers by email, roll out, and iterate: each new bundle carries a higher version code.
- Complete the listing obligations. Store listing, screenshots, privacy policy, the Data safety form, content rating and target audience. All of it is required before any public release.
- Promote to production. Closed testing first if your account is subject to it, then production. Google's review usually takes a few days, and staged rollout lets you limit the first wave to a percentage of users.
Publishing to Google Play from Cadrant
If your app is a Cadrant mobile project, the build and delivery are guided, and both accounts stay yours: the build runs on your Expo account (15 Android builds a month on the free plan), and the app bundle lands in your Play Console. Since Google has no API to create an app, two actions remain on your side once in Play Console:
- Create the app with the provided package name: Cadrant gives you the package name to paste as is at creation time.
- Invite the service account: you add it under Users and permissions with the right to release to testing tracks, then Cadrant verifies the access without uploading anything.
- The upload key is managed for you: Cadrant generates the keystore that signs your builds and keeps it for the life of the app; Play App Signing keeps the final key on Google's side.
- Every publish lands in internal testing: the release arrives as a draft on the internal track, you roll it out to your testers and promote it when ready.
The short version
- $25 once, a signed app bundle, and a review that only happens at the production step.
- Recent personal account: start recruiting the 12 testers on day one, that is the real critical path.
- Data safety, content rating and the privacy policy can be filled in early: nothing forces you to wait for the end of development.