Publishing an Android app on Google Play in 2026 involves more steps than most tutorials describe. The biggest surprise for first-time developers: you cannot go straight to a public launch. Google requires a mandatory closed testing period first. This guide covers every step in the right order.
Before You Start: Requirements
- Google Play Developer account ($25 one-time registration fee)
- Signed APK or Android App Bundle (AAB) — AAB preferred
- Privacy policy hosted at a public URL
- App screenshots (phone + tablet), feature graphic (1024×500)
- Short description (80 chars) and full description (4000 chars)
- Data Safety form completed
Step 1: Create Your Google Play Developer Account
Go to play.google.com/console and sign in with a Google account. Pay the $25 registration fee. Choose "Personal" for individual developers or "Organization" for businesses. Note: Organization accounts have different (less strict) publishing requirements than personal accounts.
Step 2: Create Your App in Play Console
Click "Create app" in Play Console. Enter your app name, default language, app or game category, and whether it's free or paid. Accept the developer policies. This creates your app's entry in the system — you haven't published anything yet.
Step 3: Complete the Store Listing
Fill out everything in the "Store presence" section: title, short description, full description, screenshots, feature graphic, app icon. This is what users see on Google Play. Google reviewers also evaluate this for policy compliance.
Important: Don't use emoji in your app title for most categories. Don't keyword-stuff your description. Take real screenshots from an actual Android device, not mockups.
Step 4: Set Up Internal Testing (Optional but Recommended)
Before involving external testers, use the Internal Testing track to test with your own team (up to 100 people). Upload your APK/AAB here, share the opt-in link with yourself and teammates, install the app, and make sure it doesn't crash. Fix any critical bugs before moving to closed testing.
Step 5: Set Up Closed Testing (Required)
This is the step that surprises most first-time developers. Go to Testing → Closed Testing. Create a track (or use the default "Alpha" track). Upload your AAB. Set up a tester group. Publish the track.
Then copy the opt-in URL from your track settings. You need at least 12 real Android users to click this link, install your app, and remain as active testers for 14 consecutive days. This is mandatory. You cannot apply for production access without it.
Step 6: Get 12+ Testers Opted In
This is where most developers get stuck. Your options:
- Ask friends/family: Works if you know 12+ Android users willing to commit 14 days. Most developers don't.
- Post in r/androiddev or r/betatestingapps: Slow, unreliable, high dropout rate.
- Use TestLaunch Pro: 25 real testers delivered within 6 hours, active for 16 days. Fastest path to production.
Step 7: Wait 14 Consecutive Days
Once 12+ testers are opted in and active, the 14-day clock starts. You can monitor your count in Play Console → Closed Testing → your track → Testers. The count shows how many testers are currently opted in.
Do not remove testers or take your track offline during this period. If the count drops below 12, the requirement resets.
Step 8: Complete the Data Safety Section
While waiting for your 14 days to complete, finish the Data Safety form in Play Console. You must disclose every type of data your app collects, why you collect it, whether you share it with third parties, and whether users can request deletion. This must be accurate — misrepresentation is a policy violation.
Step 9: Apply for Production Access
After 14 days, Play Console shows a notification that you're eligible to apply for production access. You'll fill out a short application with three essay questions about your testing experience. Google reviews this manually, typically within 3-7 days.
Your answers need to reference real data from your testing period. If you used TestLaunch Pro's Compliance Guarantee package, you receive Form Filler answers based on your actual testing logs.
Step 10: Launch
Once approved, go to Production in Play Console. Upload your AAB, complete the release notes, and roll out to 100% of users. Your app is now live on Google Play globally.
Timeline Expectations
| Step | Minimum Time | With TestLaunch Pro |
|---|---|---|
| Account setup + store listing | 1-3 days | 1-3 days |
| Recruiting 12 testers | 1-3 weeks | 6 hours |
| 14-day testing period | 14 days | 16 days |
| Production access review | 3-7 days | 3-7 days |
| Total to launch | 5-8 weeks | ~20 days |