How to Publish an App on Google Play, Step by Step

To publish an app on Google Play, create a Play Console developer account, create and set up your app, test it, then roll out a production release. New personal accounts created after November 13, 2023 must first run a closed test with at least 12 testers opted in for 14 continuous days and apply for production access.

Publishing an app on Google Play is a sequence of stages in Play Console, and each one unlocks the next. This guide walks through the whole route, from creating a developer account to a live production release, with a short summary of each step and a link to our deeper guide for it. Every fact comes from Google's Play Console Help Center, mainly Get started with Play Console, Create and set up your app, App testing requirements for new personal developer accounts and Publish your app.

If you opened a personal developer account after November 13, 2023, plan for the closed test from the start: it is the step that takes the longest, and production stays locked until it is done.

Step 1: How do you create a developer account?

You sign up for a Play Console developer account with your Google Account. Google lists these steps:

  1. Sign up. You must be at least 18 years of age to sign up for a Play Console account.
  2. Accept the Developer Distribution Agreement. You review and accept the Google Play Developer Distribution Agreement during signup.
  3. Pay the registration fee. Google charges a US$25 one-time registration fee.
  4. Choose an account type. Personal or organization; see below.
  5. Verify your developer identity information. Google says you may be asked for a valid government ID under your legal name.
  6. Personal accounts only: meet the testing and device verification requirements. Personal accounts created after November 13, 2023 must meet the testing requirements, and Google says new personal accounts must verify that they have access to an Android device using the Play Console mobile app before they can make their app available on Google Play.

On account types, Google's Choose a developer account type says both personal and organization accounts have access to the same functionality. A personal account is for personal use, for example a student, hobbyist or amateur developer. An organization account is for a business or organization, and needs a D-U-N-S number. Our guide to closed testing requirements covers the difference in detail, including which services Google says should use an organization account.

Step 2: How do you create your app in Play Console?

Once you have an account, Google's steps to create an app are: open Play Console and select Home > Create app; choose a default language and the app name as you want it to appear on Google Play; say whether it is an app or a game, and whether it is free or paid; add a contact email address for users; acknowledge the Developer Program Policies and US export laws declarations; accept the Play App Signing Terms of Service; and select Create app.

Choose your package name carefully. Google says package names for app files are unique and permanent, and can't be deleted or re-used in the future. When you create your first release, you configure Play App Signing.

Step 3: What does app setup include?

After you create the app, its Dashboard guides you through the setup tasks. Google says you start by providing details about your app's content and entering information for your Google Play listing. Your store listing has an app name of up to 30 characters, a short description of up to 80 characters and a full description of up to 4,000 characters, and Google notes that the store listing is shared across tracks, including testing tracks.

Completing app setup matters for testing: Google lists completed app setup as the requirement for access to the closed testing track. Google also warns that repetitive or irrelevant use of keywords in your app name or description can result in an app being suspended.

Step 4: Should you run an internal test?

Internal testing is optional, but Google recommends it as a starting point. It lets you share builds quickly with up to 100 testers you add by email, and it is the only track you can use before app setup is complete. Google says builds become available to internal testers within minutes.

One rule catches many developers: a user who opts in to your internal test is not eligible for your closed or open test until they opt out of the internal test. Our guide to internal vs closed vs open testing compares the three tracks.

Step 5: How do you run the closed test?

For personal accounts created after November 13, 2023, this is the required step. Google says you must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Until you meet this, Production and Pre-registration stay disabled in Play Console. Testers who opt in, test for fewer than 14 days and then opt out do not count.

The setup, in short: go to Test and release > Testing > Closed testing, click Manage track, add testers with an email list or a Google Group, add a feedback channel, create and roll out a release, then share the opt-in link. Google notes that the opt-in link displays only when the app status is Published, and that after the first publication the link can take several hours to become available.

Use the 14 days well. Google suggests recruiting testers who represent your intended audience, giving them clear instructions on how to test and report bugs, and keeping a record of their feedback, because you must summarize it when you apply. Running a pre-launch report during the test helps you find crashes and other issues before reaching users.

Step 6: How do you apply for production access?

When at least 12 testers have been opted in continuously for the preceding 14 days, open the Dashboard in Play Console and click Apply for production. The form has three sections: About your closed test, About your app/game and About your production readiness. Google says review usually takes seven days or less, but can occasionally take longer, and the account owner receives an email when it is complete.

Google names two reasons an app may need continued testing: fewer than 12 opted-in testers, and insufficient tester engagement. It also says making sure your app complies with all Developer Content Policies is your responsibility before you apply.

Step 7: How do you release to production?

Once the application is approved, you can access your app's Production page (Test and release > Production) and distribute your app to users on Google Play. Open testing also becomes available at that point. Google's Prepare and roll out a release describes the release steps: create a new release, add your app bundles, name the release and add release notes, review any errors, and start the rollout.

To publish a draft app, Google's Publish your app says you roll out a release, and at the end of the release process clicking Release also publishes your app. If an Errors summary appears, you can't publish until the errors are resolved. Google notes that for certain developer accounts it takes more time to review apps, which may result in review times of up to seven days or longer in exceptional cases. With managed publishing, you control when approved changes go live.

How do you know your app is live?

Play Console shows your app's publishing status under the app name. Google lists the app statuses, including:

  • Draft: no presence on Google Play yet, either because it hasn't been published or because it was rejected in review.
  • Internal testing: available to internal testers via URL only, not discoverable on Google Play.
  • Closed testing: discoverable on Google Play, but only selected testers can install and use it.
  • Open testing: discoverable on Google Play, and any user can become a tester.
  • Production: available for download to Google Play users in your chosen countries or regions.

For how long each stage can take, using only the times Google publishes, see our closed testing timeline.

What about Android developer verification?

Android developer verification is a separate Google program that links apps to verified developers. Google says that for most Play developers no new identity action is required, and that when you create an app in Play Console, Google Play registers the package name automatically. Our guide to Android developer verification explains what Google says.

Frequently asked questions

How much does a Google Play developer account cost?

Google charges a US$25 one-time registration fee when you sign up for a Play Console developer account.

Do I have to run a closed test before publishing?

If you have a personal developer account created after November 13, 2023, yes. Google requires a closed test with at least 12 testers opted in continuously for at least 14 days before you can apply for production access.

Can I change my package name after uploading my app?

No. Google says package names are unique and permanent, and once you upload an artifact the package name for that app is fixed. Package names cannot be deleted or reused.

How long does Google take to review an app?

Google says that for certain developer accounts it takes more time to review apps, which may result in review times of up to seven days or longer in exceptional cases. The production access review usually takes seven days or less.