Publishing your first Android app on Google Play is exciting — but the process has more steps than most developers expect. Between Play Console setup, policy forms, closed testing, and production access approval, a first launch can take four to eight weeks if you are unprepared. This checklist walks you through every stage so nothing blocks your release.

Before you start: what you need ready

Google Play developer account ($25 one-time fee)
Signed Android App Bundle (AAB) — not APK for new apps
App icon (512×512), feature graphic, and at least 2 phone screenshots
Privacy policy URL hosted on a public website
Short and full app description written for your target users
Content rating questionnaire answers
Data safety form answers (what data you collect and why)

Step 1: Create your Play Console app

In Play Console, click Create app, enter your app name, default language, and app or game type. Accept the declarations. You will land on the app dashboard with a task list — treat that list as your launch roadmap. Every unchecked item can block release.

Step 2: Complete policy and compliance forms

Google requires several declarations before any release track goes live. The most common bottlenecks for indie developers are the privacy policy link, Data safety section, and content rating (IARC questionnaire). Answer honestly — mismatches between your app behavior and your declarations cause rejections.

Data safety tips

Declare every SDK that collects data (analytics, ads, auth)
Match your privacy policy to what you declare
If you use Firebase Analytics, declare analytics data collection
Update Data safety whenever you add a new SDK

Step 3: Upload to closed testing

New personal developer accounts cannot skip straight to production. Upload your AAB to the closed testing track first. Create a release, add release notes, and roll it out. Then share your closed testing opt-in link with real testers — aim for 20+ people who actually install and open the app.

Step 4: Run closed testing for 14+ days

Keep your closed test running with enough opted-in testers for at least two weeks. Monitor crash rate and ANRs in Play Console. Fix critical bugs and upload updated builds to the same track if needed. Do not remove testers mid-test unless you replace them immediately.

Step 5: Request production access

When Play Console shows you are eligible, submit the production access request. Describe your app clearly, explain your testing process, and confirm you followed policy. Review can take several days to two weeks. After approval, the production track unlocks and you can publish to everyone.

Step 6: Ship to production

Promote your tested release to production or upload a final build
Set pricing and countries (free or paid)
Choose staged rollout (recommended) or full rollout
Submit for review — first production review can take 1–7 days
Monitor vitals and user reviews after launch

Where developers lose the most time

Tester recruitment is the number one delay. Forums and friend groups dry up quickly. Fake testers or bought installs risk account bans. PlayStorePass solves this with a done-for-you closed testing package: 20+ real testers assigned to your app, WhatsApp progress updates, and a clear path to production access — from $10 for one app.

Final checklist before you apply for production

20+ testers opted in and active in closed testing
14+ days of continuous testing completed
Crash-free rate above 98% on tested builds
Store listing complete with screenshots and descriptions
Privacy policy, Data safety, and content rating all done
No critical policy warnings in Play Console inbox

How to Publish Your First Android App on Google Play (2026 Checklist)