Google Play Console — Complete 2026 Series
Your account is ready and (for personal accounts) closed testing is done. Now comes the part everyone waits for: publishing your first app on Google Play. This is the full 2026 checklist, in order.
Get these store-listing and compliance items right the first time and you avoid the review delays covered in Part 5.
In this guide
1. Prepare Your App Bundle (AAB)
- Build a signed Android App Bundle (.aab) — Google Play no longer accepts new APKs for production.
- Enrol in Play App Signing so Google manages your signing key securely.
- Set a unique applicationId (package name) — it can never be changed once published.
- Target the current required API level for 2026 or your upload will be rejected.
2. Complete the Store Listing
| Asset | Requirement |
|---|---|
| App name | Up to 30 characters, no keyword stuffing. |
| Short description | Up to 80 characters — your hook. |
| Full description | Up to 4000 characters, natural language. |
| App icon | 512×512 PNG, 32-bit. |
| Feature graphic | 1024×500 — shown at the top of your listing. |
| Screenshots | At least 2 per form factor (phone, tablet). |
Tip: Your title, short description and screenshots drive most of your Play Store conversions. Write for humans first, keywords second.
3. Content, Data Safety & Policy Forms
These declarations are mandatory — an incomplete form is the most common reason a first release stalls.
Data safety form
Declare exactly what data you collect, why, and whether it's shared. It must match your privacy policy.
Content rating
Complete the IARC questionnaire honestly to get your age rating.
Target audience
Declare your age groups; apps for children face stricter policies.
Privacy policy URL
A reachable https:// privacy policy is required for almost every app.
4. Create the Production Release
Upload your signed AAB.
Describe what's new for users.
Start with a staged rollout to catch issues early.
First reviews can take several days. Then your app goes live 🎉