How to Publish an App on Google Play: Step-by-Step
Unlike Apple’s single App Review model, Google Play uses a system of tracks — from internal testing to production, with different levels of scrutiny at each stage. Here’s the process, step by step.
Step 1: Create the app in Play Console
- Open Play Console → All apps → Create app.
- Enter the app name, default language, type (app/game), and free or paid.
- Confirm compliance with Developer Program Policies and US export laws.
Step 2: Fill out the Store Listing and Data Safety section
- Main store listing — short and full description, icon, screenshots, feature graphic, category.
- Data safety section — a mandatory declaration: what data the app collects, whether it’s shared with third parties, and how it’s used. A mismatch between this declaration and the app’s actual behavior is a common cause of rejection at review.
- Content rating — completing the IARC questionnaire to get an age rating.
- Target audience and content — specifying your target age group, which affects additional requirements (e.g., for apps aimed at children).
Step 3: Go through the testing tracks
Google Play uses several testing levels before production:
| Track | Purpose |
|---|---|
| Internal testing | Up to 100 testers, near-instant publishing, for quickly checking a build |
| Closed testing | A limited group of invited testers, mandatory for new Personal accounts (minimum 12 testers, 14 days) |
| Open testing | Public testing, open to anyone via a link |
| Production | The final public release |
For new Personal accounts, closed testing is mandatory before your first production release — it’s not optional. Organization accounts are exempt.
Step 4: Upload a build
- Build an Android App Bundle (
.aab) — Google Play requires this format for new apps; direct APK uploads to production are no longer accepted for new publications. - Upload the file to your chosen track via Play Console → Testing/Production → Create new release.
- Fill in release notes.
- Play Console automatically checks the build against technical requirements before publishing the release.
Step 5: Staged rollout
For production releases, Google Play lets you gradually increase the percentage of users who receive an update (e.g., start at 10%, then ramp up to 100%) — this lets you catch critical issues on a small audience before a full release.
How long review takes
A new app’s first publication is usually reviewed longer (can take a few days); subsequent updates are typically faster, sometimes just a few hours — but timelines aren’t guaranteed and depend on current load on Google’s review system.
Common reasons for rejection
- Data Safety declaration doesn’t match actual app behavior — one of the most common reasons in 2025–2026, as Google has ramped up automated checks on this section.
- Permissions policy violations — requesting excessive permissions without clear justification in the app’s functionality.
- Deceptive behavior — ads disguised as system notifications, hidden paid subscriptions.
- Intellectual property policy violations — using others’ trademarks in the app name/icon without rights.
- Security issues flagged by automated scanning (malicious code, unsafe network requests).
What to do if you’re rejected
- Read Google’s notice for the specific policy violated.
- Fix the app or its description/declarations to match the flagged issue.
- File an appeal through Play Console if you believe the decision is wrong — with a specific explanation of why.
- Republish after making fixes.
FAQ
Can I skip closed testing for a personal account if the app was already tested on other platforms?
No — this is a Google Play–specific requirement, unrelated to testing done on other app stores.
What is staged rollout, and is it mandatory?
It’s an optional gradual-release mechanism — you can release to 100% of users immediately, but a staged approach reduces audience risk if a critical bug turns up.
Does review time differ for games vs regular apps?
There’s no explicit official difference by app type, but more complex apps with a wider set of permissions and features tend to take longer on average.
This article is independent and not affiliated with Google LLC. For official policies, see support.google.com/googleplay/android-developer.
Related: Setting Up a Service Account for Google Play Developer API · Google Play Console Roles and Permissions · Google Play Console Identity Verification