Course outline +
Key takeaways
- 01Personal developer accounts created after 13 Nov 2023 must run a closed test with at least 12 opted-in testers for 14 continuous days before applying for production access.
- 02Testers need to genuinely use the app: opt-in alone can lead to rejection for insufficient testing.
- 03Prepare listing text, assets, keywords and tracking before launch day so you have a baseline.
- 04Launch with a staged rollout and watch Android vitals daily.
- 05In the first 30 days, focus on reviews, stability and which keywords start to rank.
A launch is when your listing gets its first impressions, reviews and ranking signals: the foundations everything else builds on. This checklist covers Google Play’s testing requirement, what to prepare, what to do in launch week and a 30-day plan.
Phase 0: The testing requirement (new personal accounts)
| Item | Detail |
|---|---|
| Who it applies to | Personal developer accounts created after 13 November 2023 |
| What’s required | A closed test with at least 12 testers opted in continuously for at least 14 days |
| History | Reduced from 20 to 12 testers in December 2024; the 14-day period is unchanged |
| Per app | Each new app needs its own closed test before applying for production access |
| Exempt | Organization accounts, older personal accounts, and updates to apps already in production |
| Engagement | Testers should actually use the app; low engagement can lead to rejection |
Phase 1: Prepare your listing (2–3 weeks before)
- Keyword research: shortlist 10–20 realistic keywords.
- Title (≤30) with your main keyword; short description (≤80); structured long description (≤4,000).
- Icon 512×512 PNG; feature graphic 1024×500; at least 4 screenshots at 1080 px+; optional promo video.
- Privacy policy URL and accurate Data safety section.
- Content rating questionnaire and target audience settings.
- Set up keyword tracking now so you have a baseline from day one.
Phase 2: Pre-registration (optional)
If you have an audience before launch, Google Play pre-registration lets people sign up to be notified when your app is available. It’s useful when you can drive traffic from a website, community or social media before release.
Phase 3: Launch week
| Day | Actions |
|---|---|
| Day 1 | Staged rollout (e.g. 10–20%); check Android vitals; share your tracked store link on your site and socials |
| Days 2–3 | Increase rollout if vitals are healthy; reply to every review |
| Days 4–5 | Trigger the In-App Review API after success moments for testers and early users |
| Days 6–7 | Review which keywords appear in the top 100; note early search terms in Play Console |
Phase 4: The first 30 days
- Double down on keywords that start ranking: reinforce them in your short and long description.
- Replace keywords you don’t appear for after 3–4 weeks.
- Fix the most common complaint in reviews and reply when it ships.
- Run your first store listing experiment on screenshot one.
- Plan your first localization if another country is sending traffic.
- +Recruit real testers who will use the app.
- +Launch with complete, polished assets.
- +Watch vitals daily in launch week.
- +Track rankings from day one.
- −Rely on opt-ins who never open the app.
- −Launch with placeholder screenshots.
- −Push to 100% immediately.
- −Wait a month to start measuring.
How many testers do I need for Google Play?+
For personal developer accounts created after 13 November 2023: at least 12 testers opted in for at least 14 continuous days in a closed test, before applying for production access.
Do updates need testers too?+
No. Once an app has production access, updates don’t need a new closed test.
Does an organization account need the closed test?+
No: the requirement applies to newer personal accounts.
Sources
- 01Play Console Help: App testing requirements for new personal developer accounts
- 02Play Console Help: Add preview assets to showcase your app
Specifications and figures are as published by Google and the listed sources at the time of writing (23 Sept 2026); check Play Console for the latest.