How to publish an app on Google Play, including the 12-tester test

What are the steps to publish an app on Google Play?

Publishing on Google Play is a sequence of Play Console tasks, and for a new personal account one of them takes at least two weeks. Start early. If your app is not built yet, the Android app guide comes first. For the equivalent Apple process, see publishing on the App Store.

1. Register a Play Console developer account and pay the one-off fee.
2. Verify your identity and, for a personal account, verify an Android device.
3. Create the app in Play Console.
4. Complete the dashboard tasks: store listing, App content declarations, pricing.
5. Upload a signed Android App Bundle to a testing track.
6. Run the closed test if your account requires it.
7. Apply for production access, then create a production release.
8. Roll out and watch the review status.

How do you register a Play Console account, and what does it cost?

Google’s Get started with Play Console guide sets out the order. You need a Google Account and you must be at least 18. The registration fee is USD 25 one-off, as of October 2026, paid by credit or debit card. Google says prepaid cards are not accepted and that card acceptance varies by location.

Two details are worth knowing before you pay. Google says you may be asked for a valid government ID and a credit card, both under your legal name, and that if the information is found to be invalid your registration fee will not be refunded. So use your real legal details and match them exactly.

Google’s guide to choosing an account type lists which kinds of app require an organization account. If your app touches money or health, read it before you register.

What is the closed-testing requirement for new personal accounts?

This is the step that surprises first-time publishers. Google’s testing requirements page says personal accounts created after November 13, 2023 must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days. Until you meet it, the Production track and pre-registration stay disabled. Accounts created before that date are not subject to it.

Once you meet the criteria you apply for production access from the Dashboard in Play Console, and you answer questions about your app’s design, your testing process and your readiness for production.

• Recruit testers before you create the track. Twelve people who opt in and stay opted in is the hard part. Friends, colleagues and early users from your own list are the realistic source.
• Add them by email address or Google Group. Each tester needs the Google Account tied to their Play Store.
• Keep them opted in for 14 days in a row. The requirement is continuous. You need 12 testers who have stayed in from the start of that window to the day you apply.
• Ship real updates during the test. Google asks you how you tested and what you changed, so use the time to fix what testers find.

Subject: Can you test my Android app for two weeks?

Hi [name],

I am about to publish [app name], [one sentence on what it does]. Google requires me to run a closed test with at least 12 people for 14 days first, and I would like you to be one of them.

What I need from you:
1. Send me the email address of the Google Account you use on your Android phone.
2. Open this link on your phone and tap Become a tester: [opt-in link from Play Console].
3. Install the app and use it a few times over the next two weeks. Please stay opted in until [date].
4. Tell me what is confusing, broken or missing. Two lines is plenty.

It takes about five minutes to set up. Thank you.
[your name]

The requirement exists so apps get real testing, and the production-access questions ask how you tested. Fill the test with people who will actually open the app and give feedback.

How do you create the app and fill in the dashboard?

Google’s Create and set up your app guide has the sequence. In Play Console choose Create app, then enter the name, a package name, the default language, whether it is an app or a game and whether it is free or paid, plus a contact email for users. You also accept the Developer Program Policies and US export law declarations and the Play App Signing terms. The package name is permanent, so choose it with care.

Then work down the Dashboard. Google’s app dashboard guide says you must complete the mandatory tasks before you can launch. The big one is the App content page, where Google’s prepare your app for review page says you can:

• add your privacy policy, which must be linked on the store listing and within the app even if the app collects no personal data
• declare whether the app contains ads, including ads from third-party SDKs
• give instructions on how to reach restricted parts of the app, such as a demo login
• describe your target audience and content
• explain any high-risk or sensitive permissions, for example SMS or call log
• receive content ratings and describe the app’s privacy and security practices

Google also lists requirements for the privacy policy page: a public URL with a valid SSL certificate, reachable worldwide without a login, shown as a standard web page rather than a PDF, and specific to your app. Host it on your own site before you start the declaration.

Account
[ ] Play Console account registered, identity verified
[ ] Personal account: Android device verified in the Play Console mobile app

App
[ ] Package name final (it cannot change)
[ ] Target API level meets Google's current requirement
[ ] Release bundle (.aab) built and signed with the upload key
[ ] Keystore backed up somewhere safe, not in the repository

Listing
[ ] Name, short description, full description
[ ] Icon, feature graphic and screenshots from the real app
[ ] Contact email

App content
[ ] Privacy policy URL live, in the listing and inside the app
[ ] Ads declaration
[ ] Target audience and content
[ ] Content rating questionnaire
[ ] Data safety answers match what the app and its SDKs do
[ ] Reviewer access instructions or demo login

Testing
[ ] Closed test running with 12+ testers opted in
[ ] Day count reaches 14 on: [date]
[ ] Production access applied for

What file do you upload, and how is it signed?

Upload an Android App Bundle, not an APK. Google’s app bundle documentation says that since August 2021 new apps are required to publish with the Android App Bundle. Google Play then generates the APKs for each device. In Android Studio you can build one with Generate Signed App Bundle from the Build menu, or with the Gradle bundleRelease task.

Signing works in two layers, per Android’s app signing documentation: you sign the bundle with an upload key before uploading it to Play Console, and Play App Signing takes care of the rest. For your first release, Play Console walks you through configuring Play App Signing. Back up the upload keystore and its password somewhere safe, outside the repository.

Check the target API level as well. Google’s target API level requirements say that from August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher, with lower minimums for Wear OS, Android Automotive OS, Android TV and Android XR. A project created with a current Android Studio normally starts in the right place.

How do you release to production and how long is review?

Once production access is granted, go to Test and release, then Production, and choose Create new release. Google’s release guide says that if Create new release is disabled you should complete any outstanding setup tasks on the Dashboard. For the first release you configure Play App Signing, add your app bundle, write release notes and review the release before rolling it out.

Google’s publish your app page says that for certain developer accounts Google takes more time to review an app, which may mean review times of up to seven days or longer in exceptional cases. It does not publish a standard review time for other accounts, so do not plan a launch date to the hour. Track the status under your app’s name in Play Console.

After launch, updates follow the same release path. Google also lets you stage a rollout to a percentage of users, which is a sensible habit for any update that changes core behavior. The next jobs are in the guides on marketing an app and making money from an app.

Still looking for something to publish? Browse the board; every idea has a generated build prompt. Have an idea you will never build? Post it so someone else can.