Launch guideDesktop and mobile apps
How to launch an Android app
If you have a new personal Google Play developer account, your launch plan starts two weeks before you think it does: Google requires at least 12 testers opted into a closed test for 14 days in a row before you can apply for production. Plan that test as your beta. After that, the store listing's title, short description and feature graphic carry most of the discovery.
Updated · platform facts checked against the official docs linked below
At a glance
Where people find Android apps
- Google Play search and categories: Title and short description matter most for search; the feature graphic shows in browse.
- Pre-registration: Collect pre-registrations for up to 90 days; users get a notification at launch.
- Product Hunt: Good if your app also has a web or iOS presence; lead with the phone UI.
- The niche community: Where your users talk about the problem the app solves.
Assets to prepare
| Asset | Spec or guidance |
|---|---|
| App icon | 512×512, 32-bit PNG, max 1024 KB.[5] |
| Feature graphic | 1024×500, JPEG or 24-bit PNG, no alpha. Required.[5] |
| Screenshots | At least 2 across device types, up to 8 per type; phone sides 320–3,840 px, long side no more than twice the short.[5] |
| Preview video | A YouTube URL; recommended especially for games.[5] |
| Title | 30 characters max; no "Free", "#1" or emoji.[3] |
| Short description | 80 characters max.[3] |
Store and listing rules
What the platform itself says, with a link to the page we checked.
- Personal accounts created after November 13, 2023 need 12 testers opted in continuously for 14 days before applying for production access. Testers who leave early don't count.[1]
- No ranking or promo claims in metadata ("#1", "Best of Play", "10% off"), and no irrelevant emoji or caps.[3]
- Some accounts and apps get extended reviews of up to seven days or longer in exceptional cases.[4]
- Pre-registration campaigns last at most 90 days; you can offer one pre-registration reward per app lifetime.[6]
A 4-week launch timeline
Week 1 · four weeks out
- Register the developer account and verify identity.
- Recruit at least 15 closed testers (a buffer over 12) who'll stay opted in.
- Start the closed test on day one of this week.
Week 2 · three weeks out
- Collect feedback and ship fixes to the closed track.
- Write the title, short and full description.
- Make the icon, feature graphic and screenshots.
Week 3 · two weeks out
- Keep testers opted in; the 14 days must be continuous.
- Set up pre-registration if you want a notification at launch.
- Build the landing page with a Get it on Google Play link.
Week 4 · launch week
- Apply for production access once the test requirement is met.
- Submit the production release; leave room for review.
- Prepare launch posts and the email to testers.
Launch-day checklist
- Roll out to production (a staged rollout lets you watch crash rates).
- Email testers and the waitlist.
- Post in the niche community and on LaunchRanked.
- Watch Android vitals and reviews; reply to early reviews.
After launch: SEO steps
Launch boards reset; search pages don't. These steps keep people finding you after launch week.
- Give the app a web page with real content and a Play link; the Play page ranks mostly for your name.
- Add
SoftwareApplicationmarkup withoperatingSystem: Androidand price. - Target task searches ("{job} app Android") with feature pages.
- Localize the listing for your biggest markets.
Common mistakes
- Not knowing about the 12-tester, 14-day requirement until launch week.
- Testers who opt out early, restarting their clock.
- "Free" or emoji in the title, which breaks the metadata policy.
- Launching without a feature graphic, which is required.
Templates for this launch
- App store descriptionFill-in App Store and Google Play listing copy within each store's limits: name, subtitle, promo text, short and full description, keywords.
- Beta invite emailA beta invite email that sets expectations: what's ready, what's rough, what you need from testers and how to report bugs, with a filled example.
- Release notesRelease notes for a notable launch or version: what's new, why it matters, how to use it, upgrade steps and known issues, with a filled example.
FAQ
Do I need 12 testers to publish on Google Play?
If you have a personal developer account created after November 13, 2023, yes: at least 12 testers opted into a closed test for the preceding 14 days, continuously, before you can apply for production.
How long does Google Play review take?
Google says some accounts and apps get extended reviews of up to seven days, or longer in exceptional cases.
What are the Play Store text limits?
Title 30 characters, short description 80 characters, full description 4,000 characters.
Is pre-registration worth it?
It lets people sign up before launch and get a notification when you go live. Campaigns can run up to 90 days.
Sources
- Play Console Help: Testing requirements for new personal developer accounts
- Play Console Help: Get started with Play Console
- Play Console Help: Metadata policy and store listing
- Play Console Help: Prepare your app for review
- Play Console Help: Add preview assets
- Play Console Help: Pre-registration
Checked . Platforms change their rules; open the source before you rely on a number.
Related launch guides
- How to launch an iOS appiOS app launch guide: App Store screenshot sizes, text limits, review times, TestFlight, guideline traps like account deletion, and web SEO for your app.
- How to launch a mobile gameLaunch a mobile game on iOS and Google Play: pre-registration, TestFlight, store assets, preview videos, soft launches and communities that find new games.
- How to launch a Windows appWindows app launch guide: free Microsoft Store developer accounts, MSI/EXE certification, screenshot sizes, winget, code signing and web SEO.
- How to launch a Mac appMac app launch guide: Mac App Store vs direct download, sandboxing, notarization, screenshot sizes, Setapp, and the communities where Mac users find apps.