How to Publish an App
on Google Play Store
A complete step-by-step guide, from creating your developer account to getting your app live.
New personal account? You need testers before you can publish.
Accounts created after November 2023 must complete closed testing with 12+ testers for 14 days. Organization accounts are exempt. Get professional testers →
What we'll cover
Create a Developer Account
Go to play.google.com/console, sign in with your Google account, and pay the $25 one-time registration fee.
You'll need to verify your identity with a government ID. For personal accounts, you'll also verify device access via the Play Console mobile app. Account approval takes up to 48 hours.
Personal vs Organization account
Prepare Your App
Before uploading to Google Play, make sure you have all of these ready:
Signed AAB file
Google requires Android App Bundles (.aab), not APKs. Build a signed release bundle from Android Studio or use your framework's release command. The bundle must be signed with your upload key.
Privacy policy URL
A publicly accessible privacy policy page that explains what data your app collects, how it is used, and how users can request deletion. This URL must be live and not return a 404.
Phone and tablet screenshots
At least 2 phone screenshots are required (recommended 4 to 8) in JPEG or PNG format around 1080 x 1920 px. Tablet screenshots are optional but recommended to improve your store listing quality and visibility on larger devices.
App icon (512 x 512 px)
A high-resolution app icon in 32-bit PNG format. This is displayed on the Play Store listing, search results, and recommendations.
Feature graphic (1024 x 500 px)
A banner image displayed at the top of your store listing. Required in JPEG or PNG format. This is the first visual users see when they visit your app page.
AAB generation varies by framework. Flutter uses flutter build appbundle, React Native uses ./gradlew bundleRelease, and native Android uses the "Generate Signed Bundle" wizard in Android Studio.
Create Your Store Listing
In Play Console, create a new app and fill out the Main Store Listing. This is what users see before they install your app.
Text fields
Required graphic assets
Privacy Policy URL is mandatory
You must link a publicly accessible privacy policy page. It must explain what data you collect, how it's used, and how users can request deletion. No privacy policy = instant rejection.
Complete Compliance Forms
Google requires three compliance forms before you can publish. These can't be skipped. Play Console will flag them as incomplete.
AContent Rating
Complete the IARC questionnaire about your app's content: violence, language, sexuality, etc. Takes about 5 minutes, the rating is generated instantly, and it's free.
BData Safety
Declare what data your app collects and shares. This includes data collected by third-party SDKs like Firebase Analytics, Crashlytics, AdMob, or any social login provider.
CTarget Audience
Declare the age group your app is designed for. If your app isn't built for children, select "18 and over" to avoid being subject to the stricter Families Policy, which has tight restrictions on ads, data collection, and content.
Closed Testing
For personal accounts created after November 2023. Skip if you have an organization account.
Closed testing is a pre-release track where a limited set of testers can download and use your app. Google uses this to confirm real people have tested your app before it goes public.
How to set it up
- 1
Go to Release → Testing → Closed testing → Create track
- 2
Add an email list with at least 12 Gmail addresses of your testers
- 3
Upload your signed AAB and submit the closed testing release for review (Google takes 3–5 days)
- 4
Share the opt-in link with testers. They must click it and install the app themselves.
- 5
Wait 14 days then return to Play Console and apply for production access
Aim for 20–25 testers as a buffer in case some don't complete the opt-in. Adding an email address doesn't count. Testers must click the opt-in link. Once opted-in, uninstalling doesn't remove them from your count.
Don't have testers? Two ways to get them.
Community App
Join 50,000+ developers who exchange tests for free. Test someone's app, earn credits, use them to get testers for yours.
Paid Testing Plans
25 verified testers opt in within 6 hours and stay active for 14 days. Production access guarantee or full refund.
Submit for Review
Once closed testing is complete (or if you have an organization account), go to Release → Production → Create new release, upload your signed AAB, write release notes, and hit Submit.
Review time: Most apps are reviewed within a few hours to 3 days. Apps with sensitive permissions or first-time submissions can take up to 7 days.
Common rejection reasons to avoid
Ready to Publish?
Stuck on the closed testing step? We provide 25 professional testers with a production access guarantee.