How to Publish an App on Google Play Store

Publishing an Android app on Google Play involves more than uploading an APK. For developer accounts created after November 2023, mandatory closed testing adds 14+ days to your timeline. This guide walks through every required step in order.

Prerequisites Before You Start

Before creating your developer account, have these ready:

• A Google account (Gmail) to use as your developer account
• A signed release APK or Android App Bundle (AAB)
• App screenshots (minimum 2 for phone)
• Feature graphic (1024×500 pixels)
• App icon (512×512 pixels, PNG)
• A live privacy policy URL if your app collects any user data
• A valid payment method for the $25 developer registration fee

Step 1: Create a Google Play Developer Account

Go to play.google.com/console and sign in with your Google account. You will be prompted to pay a one-time $25 USD registration fee. This fee is non-refundable and covers the lifetime of the account.

After payment, new personal accounts created after November 13, 2023 must complete identity verification. You will upload a government-issued photo ID (passport, driver's license, or national ID card) and take a selfie. Processing takes 1–3 business days.

Organization accounts require a D-U-N-S number for business verification. If you do not have one, allow up to 30 business days to obtain it through Dun & Bradstreet. Start this process early.

Step 2: Create Your App in Play Console

Once your account is verified, click Create app in the Play Console dashboard. You will be asked to:

• Enter the app name (as it will appear on the Play Store)
• Select the default language
• Choose whether it is an app or a game
• Specify whether it is free or paid
• Accept the developer policies

This creates the app entry in Play Console. Nothing is visible to users yet.

Step 3: Complete Your Store Listing

Navigate to Store presence > Main store listing. Required fields:

• Short description (up to 80 characters) — displayed in search results
• Full description (up to 4000 characters) — key for keyword indexing
• Phone screenshots (minimum 2, maximum 8 — minimum 320px on shortest side, maximum 3840px on longest)
• Feature graphic (1024×500 pixels, JPG or PNG)
• Hi-res app icon (512×512 pixels, PNG, no alpha channel)

If your app supports tablets, provide tablet screenshots as well. Apps without tablet screenshots will not appear in tablet search results.

Screenshots must show the actual app. Using generic mockups or illustrations that do not match the real app is a policy violation and will cause rejection during review.

Step 4: Complete Required Policy Forms

Under Policy, complete all of the following:

Content Rating

Complete the IARC content rating questionnaire. Answer honestly about your app's content — violence, language, adult themes, and similar. The questionnaire takes 5–10 minutes. Your rating is displayed on the Play Store and affects discoverability in certain regions and age groups.

Data Safety

Declare every type of data your app collects, processes, or shares. This includes user-provided data (name, email), usage analytics, device identifiers, and any data shared with third parties. The Data Safety section is public and appears on your store listing.

Target Audience and Content

Select who your app targets (adults, teens, children, or mixed audiences). Apps targeting children under 13 must comply with additional requirements under the Families policy and may require changes to your app.

Privacy Policy

Enter the URL of your live privacy policy. The policy must be accessible from outside the app, must be in the same language as your store listing, and must accurately describe your data practices. A generic template that does not mention your specific data types will result in rejection.

Step 5: Upload Your App to the Closed Testing Track

For new personal accounts created after November 2023, you must complete closed testing before applying for production access.

Navigate to Testing > Closed Testing. Create a closed testing track if prompted. Upload your signed release AAB or APK. Set the rollout percentage to 100% within the track.

Critical: Do not upload to Internal Testing. The Internal Testing track does not count toward the production access requirement. Only the Closed Testing track matters.

Step 6: Recruit 12+ Testers and Run the 14-Day Window

This is the most time-consuming step for most developers. Google requires a minimum of 12 unique testers who:

• Are enrolled in your closed testing track specifically
• Have opted in via the official opt-in URL (not just received an email invite)
• Have the app installed on a real Android device
• Maintain the installation for 14 consecutive days

The 14-day counter resets to zero if your active tester count drops below 12 at any point.

How to Add Testers

The recommended method is a Google Group. Create a group at groups.google.com, add your testers' Gmail addresses, then link the group to your closed testing track in Play Console. This allows you to manage all testers as a group rather than individually.

Copy the opt-in URL from Play Console under your closed testing track. Send this URL to all testers. Each tester must open the link on their Android device, click “Become a Tester”, then download the app from the Play Store.

How to Keep Testers Active

• Recruit 16–20 testers to absorb drop-offs (a buffer of 4–8 above minimum)
• Send a day-5 check-in asking testers to confirm the app is still installed
• Send a day-10 reminder that you are approaching the end of the window
• Push at least one minor app update mid-window — it sends testers a notification and reminds them the app exists
• Monitor the active tester count in Play Console daily

If recruiting testers is the bottleneck for your launch, a managed testing service provides an immediate pool of committed testers. The 14 days run uninterrupted and you receive a participation log for the production access questionnaire.

Step 7: Apply for Production Access

After 14 continuous days with 12+ active testers, navigate to your app's Production section in Play Console. The “Apply for production access” button will be active.

The Questionnaire

Google asks a series of questions about your testing process. Answer each question specifically and with enough detail. Each field should have at least 250 characters. Questions typically cover:

• How you recruited your testers and how many participated
• What features testers used and how they interacted with the app
• What feedback or bug reports you received
• What changes you made to the app based on testing feedback
• Why you believe the app is ready for public distribution

If you used a testing service that provided a participation log, reference specific data from that log. Generic answers (“testers found it worked well”) increase rejection risk.

Step 8: Wait for Review and Publish

Google reviews production access applications within 3–7 business days. You will receive an email when a decision is made.

If approved: navigate to your app's Production track, upload your final release build if you have not already, and roll out to 100%. The app will appear on the Play Store within a few hours.

If rejected: read the rejection email carefully, address every stated issue, and reapply. Do not appeal without first fixing the issues listed.

Common Reasons for Rejection

• Store listing screenshots do not match the actual app
• Privacy policy does not accurately reflect data collection
• Production access questionnaire answers are too brief or non-specific
• App requests permissions not justified by its core function
• Tester activity signals were too low (installs with no engagement)
• Developer account has an unresolved policy issue

Total Timeline to Expect

• Account setup + verification: 1–5 days
• Store listing + forms: 1–2 days
• Tester recruitment: 1 day (managed service) to 7 days (self-recruited)
• 14-day testing window: 14 days minimum
• Application + Google review: 4–10 days
• Minimum total: approximately 21–30 days