How to Publish an Android App on Google Play in 2026
Last updated: June 2026 · 10 min read
Publishing an Android app on Google Play in 2026 is more involved than it used to be. With the introduction of the Closed Testing requirement, the process now takes a minimum of 2-3 weeks from account creation to production release. This guide walks you through every step. If you need testers fast, TesterBee delivers 12 real testers within 24 hours.
Create a Google Play Developer account
Sign up at play.google.com/console. Pay the one-time $25 registration fee. Verify your identity with a government-issued ID. Complete your developer profile with a display name, email, and website.
Pro tip: Use a dedicated Google account for your developer profile, not your personal Gmail. This keeps your developer communications organized.
Prepare your app assets
Design your app icon (512x512px), feature graphic (1024x500px), and at least 2-8 screenshots per device type (phone, 7-inch tablet, 10-inch tablet). Write a compelling short description (80 characters) and full description (4,000 characters max).
Pro tip: Screenshots should show your app's best features. Use captions that highlight benefits, not just feature names.
Set up closed testing
Upload your app bundle (AAB) to the Closed Testing track in Google Play Console. Create an opt-in link or email list for testers. Recruit 12+ real testers with unique Google accounts and Android devices.
Pro tip: Use TesterBee to get 12 real testers within 24 hours instead of spending weeks recruiting manually.
Run the 14-day testing period
Testers install your app via the Play Store opt-in link and use it for 14 consecutive days. Monitor engagement, collect feedback, and fix bugs. Ensure at least 12 testers remain active throughout.
Pro tip: Recruit 14-15 testers to have a buffer against dropouts. Replace inactive testers immediately.
Apply for production access
After 14 days of active testing, apply for production access in the Play Console. Google reviews your app, testing data, and store listing. If approved, you can publish to production.
Pro tip: Before applying, verify your store listing is complete, all crashes are fixed, and your app complies with Google Play policies.
Publish to production
Once production access is granted, create a production release in the Play Console. Upload your final app bundle, set your rollout percentage (start with 5-10% if you want a staged rollout), and submit for review.
Pro tip: Production reviews typically take a few hours to a few days. Submit during business hours for faster review times.
How long does it really take?
| Step | Minimum Time | Realistic Time |
|---|---|---|
| Developer account | 1-2 days | 2-3 days |
| App assets & listing | 1 day | 2-3 days |
| Closed Testing | 14 days | 14-21 days |
| Production access review | 1-3 days | 3-5 days |
| Production release | 1 day | 1-3 days |
| Total | 18 days | 22-35 days |
The biggest bottleneck: finding testers
As the timeline shows, Closed Testing is the longest phase. The 14 days are fixed, but the real time sink is finding 12 real testers who will stay engaged. Many developers spend 1-2 weeks just recruiting testers before the 14-day clock even starts.
TesterBee eliminates this bottleneck by providing 12 real testers within 24 hours. You start the 14-day clock the day after you sign up — not two weeks later when you finally find enough people.
Step-by-step: Publishing your app after Closed Testing approval
Once Google approves your production access application, the final steps to publish are straightforward but important. Missing one step can delay your launch:
- Create a production release. In Google Play Console, go to Production, click "Create new release," and upload the same AAB you validated during Closed Testing — or an improved version incorporating tester feedback.
- Add release notes. Write clear release notes for your first production version. Mention that this is the initial release. Keep it professional — your release notes are visible to users browsing your app on the Play Store.
- Select rollout percentage. For your first release, you can choose "Full rollout" (100% of users) or a "Staged rollout" (start with a smaller percentage and increase over time). Staged rollouts let you catch production issues before they affect all users.
- Review and confirm. Google Play Console shows a summary of your release — the AAB version, supported devices, permissions, and content rating. Review everything carefully. Once confirmed, the release goes to Google for a final review (typically a few hours to 1-2 days).
- Monitor after launch. Your first 24-48 hours in production are critical. Watch crash rates, user reviews, and any Play Console alerts. Respond to early reviews — they shape your app's initial rating and ranking.
Common post-launch mistakes to avoid
Google prioritizes actively maintained apps in search and discovery. Push regular updates — even small bug fixes or content refreshes — to signal that your app is actively developed. Apps that go months without updates lose visibility.
Respond to every review, especially negative ones, within 24-48 hours. A developer who engages with feedback builds trust with both users and Google’s ranking algorithms. "Thanks for the feedback — we are working on a fix for this issue" goes a long way.
Play Console provides acquisition reports, crash data, and ratings insights. Set these up in your first week live. Understanding where your users come from and what they experience helps you make data-driven decisions about updates and marketing.
Google updates its Developer Program Policies periodically. Check the Policy center in Play Console at least once per quarter. A policy change you miss can result in your app being suspended without warning.
Frequently asked questions
How long does the final production review take?
Can I update my app immediately after publishing?
What happens if my production release is rejected?
From zero to Play Store in 18 days
TesterBee handles the hardest part — getting 12 real testers. You focus on building a great app. Full refund if Google rejects your production access.
Get 12 real testers