How to Publish an App on Google Play in 2026

In 2026, the path from a finished APK or AAB to Google Play release is stricter: newly created personal developer accounts need closed testing, complete safety disclosures, Play Console review, and then Production access. Here is the current flow step by step.

Step 1. Register a developer account

Go to play.google.com/console and sign in with a Google account. Choose your account type:

• Personal for individual developers. Registration fee: $25 once.
• Organization for companies. You will need a D-U-N-S number and legal documents.

Step 2. Create the app in Play Console

After signing in, click Create app. Fill in:

• App name
• Default language
• Type: app or game
• Paid or free

Then complete the store listing: description, screenshots, app icon, and feature graphic.

Step 3. Prepare a privacy policy

Google requires a privacy policy link for any application. Host it on your own website or use a privacy policy generator. Without it, moderation may fail.

Step 4. Prepare the release file

For Google Play, use AAB (Android App Bundle) whenever possible. Before upload, make sure the build installs on a real device, does not crash on the first screen, and meets current target API requirements. For mobile apps, Google Play currently requires Android 15 / API level 35 or higher for new apps and updates, with separate timelines for categories such as Wear OS, Android TV, and Automotive.

Step 5. Complete required Play Console sections

Before release, Play Console asks you to complete:

• App content: content rating, target audience, ads, news, medical or financial declarations where relevant.
• Data safety: what data is collected, shared, and protected.
• Privacy policy: a public URL to your privacy policy.
• App access: test login or instructions if part of the app is behind authentication.

Step 6. Pass closed testing

This is the most important and most surprising stage for new developers. Google requires:

• At least 12 testers opted in to the closed test
• A period of 14 consecutive days
• Preferably, testers install the app, open it, and leave meaningful feedback

After those conditions are met, you can request Production access from the Play Console Dashboard.

Step 7. Request Production access

After closed testing, Google asks what feedback you received, what issues you fixed, who tested the app, and why it is ready for users. Avoid generic answers. Mention real test scenarios and fixes.

Step 8. Submit the production release

After Production access is approved, create a production release, upload the final build, add release notes, and send it for review. Google says Production access review usually takes seven days or less, but it can take longer in some cases.

Mini checklist before publishing

• The build opens without crashes on a real device.
• Store listing is complete: description, icon, screenshots, and feature graphic.
• Privacy policy, Data safety, and Content rating are complete and consistent.
• Closed testing passed with 12 opted-in testers for 14 consecutive days.
• You have a short list of found issues and fixes for the Production access application.

Typical timeline

• Account registration and verification: 1-3 days, sometimes longer
• Play Console setup and first release review: 1-7 days
• Closed testing: 14 consecutive days after you have 12 participants
• Production access application: usually up to 7 days
• Final production release review: 1-7 days

In total, plan for 3-5 weeks from a ready build to publication if your assets and testers are prepared in advance.

Summary

Publishing on Google Play is not fast, but it is predictable. The main hidden barrier is closed testing, because it requires 12 real users. If you want to pass that stage without delays, we are ready to help.