Guides / Prompting and shipping

How to Publish an App on Google Play: The Real Play Console Steps

How to publish an app on Google Play: developer account, Create app, store listing, App content forms, the 12-tester closed test and production release.

Mythex Team · 2026-11-01 · 6 min read

To publish an app on Google Play, register a Google Play developer account (a one-time 25 USD fee as of November 2026), create the app in Play Console, fill in the store listing and the App content forms, upload an Android App Bundle (.aab) to a testing track, and then release it to production once Google reviews it. If you have a new personal account, there's one extra step: a closed test with at least 12 testers for 14 consecutive days before you can apply for production access. This guide walks through each screen in order, with the details that cause most delays.

If you haven't built the app yet, start with how to make an Android app.

Before you start: what you need

• The app as an Android App Bundle (.aab). Google Play requires this format for new apps.
• A target API level that's current. As of November 2026, new apps and updates must target Android 16 (API level 36).
• A privacy policy at a public web address. It must be a normal web page, not a PDF, and not behind a login.
• An icon, screenshots and a feature graphic. Check Play Console for the current size requirements; at the time of writing, the icon is 512 × 512 pixels and the feature graphic 1024 × 500.
• A support email address.
• A government ID and a card in your legal name for registration. Prepaid cards aren't accepted.

Step 1: Create your developer account

Go to Play Console and sign up. You'll choose between two account types:

• Personal. For individuals. You'll verify your identity and access to an Android device using the Play Console mobile app, and complete the testing requirement described in Step 6.
• Organisation. For registered businesses. Verification asks for business details and takes longer, but there's no 12-tester requirement.

You must be at least 18. The 25 USD fee is paid once and isn't refunded if Google judges your details invalid, so enter your legal name exactly as it appears on your ID.

Step 2: Create the app

In Play Console, click Create app and fill in:

• App name as users will see it.
• Default language.
• App or game.
• Free or paid. You can change a paid app to free later, but not a free app to paid.
• Declarations: accept the Developer Program Policies, US export laws and Play App Signing terms.

The package name (like com.yourcompany.yourapp) is set by your first upload and can never be changed or reused, so pick it carefully if you build the app yourself.

Step 3: Write the store listing

Open the Main store listing page (under Store presence in the left menu) and add:

• App name, up to 30 characters.
• Short description, up to 80 characters. This is often all people read, so lead with what the app does.
• Full description, up to 4,000 characters. Explain who it's for, the main features and anything users need to know, in plain language. Don't stuff keywords; Google's policies prohibit it.
• Graphics: icon, feature graphic and phone screenshots. Real screens from the app, not mock-ups of features that don't exist.
• Category and contact details.

Step 4: Complete the App content forms

Open the App content page (under Policy in the left menu). Each item needs an answer before you can release:

• Privacy policy URL.
• App access. If parts of the app need a login, give reviewers working credentials. Missing logins are a common reason for rejection.
• Ads. Say whether the app shows ads, including through third-party code.
• Content rating. A questionnaire that produces age ratings for each region. Skip it and the app is "Unrated", which blocks release.
• Target audience and content. The age groups the app is for. Including children brings the stricter Families policy requirements.
• Data safety. What data the app collects or shares, why, and whether it's encrypted and deletable. Answer for everything in the app, including analytics and login providers.
• Other declarations as prompted, for example for news, health, financial or government apps, or for sensitive permissions such as SMS.

Be accurate. Google compares your answers with what the app actually does.

Step 5: Upload your first build to internal testing

Open Internal testing (under Testing in the left menu), create a release and upload the .aab. On this first release you'll set up Play App Signing: let Google generate and hold the signing key unless you have a reason to manage your own. Add yourself and a few colleagues as internal testers by email, then roll out the release. Testers open the opt-in link and install the app from the Play Store.

Every later upload needs a higher versionCode than the one before.

If you build with Mythex

On the Pro plan, Mythex makes the AAB for you from your published app. You can work in either of two ways:

1. Upload it yourself. Ask the agent to build for Android, click Download when the card says Ready to upload, and upload the file in Play Console. The file stays downloadable from Project settings for about 30 days.
2. Connect your own Google Play service account. Create a service account and JSON key in Google Cloud, invite its email in Play Console under Users and permissions with access to this app, and drop the key into Mythex. From then on every Android build goes to internal testing by itself, with the version code set above anything already on Google Play. The agent can also edit the store listing, and it asks you before anything goes public, such as a production release.

Creating the app (Step 2), the Data safety form and the content rating stay in Play Console; the agent tells you when one of them is missing. Read more on the Mythex Android app builder page.

Step 6: Run a closed test (new personal accounts)

If your personal account was created after 13 November 2023, you must run a closed test with at least 12 testers who stay opted in for at least 14 days in a row before you can apply for production access. Someone who leaves and rejoins starts a fresh 14 days.

Practical tips:

• Recruit more than 12. People drop out. Aim for 15 to 20.
• Use a Google Group or an email list to manage testers.
• Ask for real use, not just an install. Google asks about your testing when you apply, and you'll learn far more.
• Ship an update during the test with fixes from feedback.

Our beta test guide covers recruiting and collecting feedback. When the 14 days are done, apply for production access from the Dashboard and answer the questions about your test.

Step 7: Release to production

Once production access is available, open Production in the left menu:

1. Choose countries and regions where the app will be available.
2. Create a new release and add the bundle from testing, or upload a new one.
3. Write release notes in plain words: what's new or fixed.
4. Review and send for review. Changes collect under Publishing overview until you send them.

Review time varies. Updates are often quick; first releases can take several days. You can choose managed publishing if you want to approve the exact moment an approved release goes live.

Step 8: After launch

• Watch Android vitals for crashes and "app not responding" reports.
• Reply to reviews, especially the early ones.
• Keep the target API level current. Google raises it each year, and apps that fall behind stop being offered to new users on newer phones.
• Update the Data safety form whenever you add new data collection.

For a web-wrapped app, such as one built with Mythex, most changes reach Android users when you publish the web app, because the phone app opens your published app. A new store release is only needed for things like the icon, name, permissions or a new target level.

Common reasons for rejection or delay

• No working login for reviewers.
• A privacy policy that's missing, a PDF, or doesn't match the Data safety answers.
• Screenshots or descriptions that promise features the app doesn't have.
• Requesting sensitive permissions the app doesn't clearly need.
• A broken or empty app: placeholder text, dead buttons.

Also publishing on iPhone?

Apple's process is different: a yearly membership, TestFlight, and a human review of every release. Read how to publish an app on the App Store for those steps.