Expert: features and shipping · Publishing on the Play Store and Firebase · topic 44 of 50 · 30 min
Google Play Console and testing tracks
Explanation
The developer account
Google Play Console is the website where developers publish and manage apps. Creating an account needs a Google account, a one-time registration fee (US$25 at the time of writing) and identity verification with official documents. You choose a personal account or an organisation account (which needs details such as a D-U-N-S number for the company). Requirements change, so read the current Play Console help pages when you sign up.
Creating the app and the store listing
| Listing item | Notes |
|---|---|
| App name | Up to 30 characters; clear, no keyword stuffing |
| Short description | Up to 80 characters; the one-line pitch |
| Full description | Up to 4,000 characters; features and benefits, honest |
| App icon | 512 x 512 PNG |
| Feature graphic | 1024 x 500 image shown at the top of the listing |
| Screenshots | At least 2 phone screenshots; tablet ones if you support tablets |
| Category, contact email, privacy policy URL | Required details |
You can add translated listings, for example in Hindi, Tamil or Bengali, to reach more users. Write the listing for people, not for search engines: misleading claims and keyword lists break Play's metadata policy.
Testing tracks
| Track | Who can install | Typical use |
|---|---|---|
| Internal testing | Up to 100 testers you add by email | Quick checks by your team, available within minutes |
| Closed testing | Testers you invite (email lists or Google Groups) | Beta with friends, customers or QA |
| Open testing | Anyone who opts in from the Play listing | Public beta |
| Production | Everyone in your chosen countries | The real release |
The closed-testing rule for new personal accounts
For personal developer accounts created after 13 November 2023, Google requires a closed test with at least 12 testers who stay opted in for at least 14 continuous days before you can apply for production access (the number was 20 until late 2024). Plan for this: recruit testers early (friends, classmates, early customers), give them a reason to use the app, and collect feedback. Check the current Play Console rules, as these numbers can change.
Rolling out
When you release an update to production, you can use a staged rollout: release to, say, 5% of users, watch crash rates and reviews in Play Console's Android vitals for a day or two, then increase to 20%, 50% and 100%. If something goes wrong, halt the rollout and fix it while most users are unaffected.
Pre-launch report
When you upload a build to a testing track, Play can automatically run it on a range of real devices and report crashes, performance problems, security warnings and accessibility issues, with screenshots. Read it before every production release.
Common mistakes
- Leaving the 12-tester closed test to the last week before a deadline.
- Screenshots that do not show the real app, or misleading claims in the description: listing rejected.
- Releasing straight to 100% of users. Use staged rollouts.
- Ignoring Android vitals: high crash or ANR rates reduce your app's visibility on Play.
Need help?
Stuck on a word or an idea? Search this course, or every course, and jump straight to the explanation or a worked question.
Try:
Watch the lesson
Google Play Console and testing tracks · 1/6
Play Console is where you publish apps. The account needs a one time fee and identity verification.
Prefer a video by a teacher? Find free videos on “google play console publish app closed testing 12 testers 14 days store listing” on YouTube ↗
In real life: A college project goes public
Three students in Nagpur build a timetable app for their college. They create a personal Play Console account, upload to internal testing for themselves, then invite 25 classmates to a closed test through a Google Group and keep it running for three weeks while fixing bugs from feedback. After getting production access, they release with a 10% staged rollout, watch the crash rate, and go to 100% after two days.
Practice (0/3 done)
Which track lets up to 100 people you add by email install a build within minutes?
Why use a staged rollout?
Prepare a complete store listing for one of your apps in a document: name (max 30 characters), short description (max 80), full description (300 to 600 words, honest), list of 4 screenshots with captions, feature graphic idea, category and a plan to recruit 12+ closed testers for 14 days.
Quick quiz
Read more (free)
Related help
Before this, learn
This topic builds on these. If something here feels new, open them first.
Related topics
- Play policies: privacy, data safety and targetsPublishing on the Play Store and Firebase · same module
- Firebase basicsPublishing on the Play Store and Firebase · same module
- Publishing on Google PlayFlutter and Dart · Publishing to the stores and the web
- Creating and securing an AWS accountCloud Computing (AWS, Azure, Google Cloud) · AWS account, IAM and billing
- Portfolio and next stepsAndroid career path
- Publishing on the Apple App StoreFlutter and Dart · Publishing to the stores and the web
Questions people ask about this
Open a question to see the answer and why. The first ones are this topic's own quiz, so try the quiz above before you peek.
What is the size of a Play Store app icon?
Answer: 512 x 512
The high-resolution icon is 512 x 512 PNG.
What is a feature graphic?
Answer: A 1024 x 500 banner image on the listing
It appears at the top of the listing.
Which track lets anyone opt in to a public beta from the listing?
Answer: Open
Open testing is public.
Where do you watch crash and ANR rates after release?
Answer: Android vitals in Play Console
Android vitals aggregates real-user data.
What is the one-time Google Play developer registration fee (at the time of writing)?Related
Why does Google raise the target API requirement every year?Related
Answer: So apps adopt newer privacy and security behaviour
Newer targets enable newer protections.
An account was created in August 2025. Which Free Tier rules apply?Related
Answer: The newer Free plan or Paid plan choice with credits
Accounts created on or after 15 July 2025 use the new Free/Paid plan model with credits. Check the Free Tier page for details.
With Play App Signing, who holds the app signing key?Related
Answer: Google
You keep the upload key; Google keeps the app signing key.
Pass the quiz (60% or more) or mark this topic as done when you are ready.
Your progress is saved on this device only.
Next steps
- 2 more topics in “Publishing on the Play Store and Firebase” before its exam: Play policies: privacy, data safety and targets, Firebase basics.
- Module 11 exam: Publishing on the Play Store and Firebase · 13 questions · 25 min, without help. 4 topics of this module still to finish first.
- Then the next module, Android career path. 50 topics left in the course before the final exam.