Google Play pre-launch checklist for new developers
15 Oct 2026 · 5 min read
Passing the closed test is only one part of launching. Play Console also blocks production until these items are complete. Work through them during your 14 days so you can publish the day you are approved.
App content (Policy → App content)
- Privacy policy — a public URL that explains what data you collect and why. Required for almost every app.
- Data safety form — declare data collected and shared, including by SDKs such as ads, analytics and crash reporting. Check each SDK's own disclosure page.
- Content rating — fill the IARC questionnaire honestly; the rating appears on your listing.
- Target audience — if children are included, extra Families policy rules apply.
- Ads — declare whether the app contains ads.
- App access — if features need a login, give reviewers a test account.
Technical
- Target API level — new apps must target a recent Android version. Play Console shows a warning if yours is too low; update
targetSdkVersionbefore your production release. - Upload an Android App Bundle (.aab) signed with Play App Signing.
- Test on at least one low-end phone and one recent phone.
Store listing
- App name (30 characters), short description (80) and full description (4,000).
- 512×512 icon, 1024×500 feature graphic, at least 2 phone screenshots.
- Category, contact email and, ideally, a website.
Need help with screenshots or keywords? TestPass offers ASO reviews and store listing screenshots as add-ons from your dashboard.
Need 12 real testers?
TestPass gives you real people on real phones, a buffer above 12 and daily feedback — from ₹999.
Start my closed test