How to Publish an App on Google Play (2026): The Full Flow
Six steps: developer account, signed AAB upload, Data Safety section, hosted privacy policy, store listing with screenshots, then staged rollout and review. Most first-submission rejections come from contradictions between these pieces — keep them describing the same app.
Step 1–2: Account, app entry, and a verified AAB
Pay Google's one-time $25 fee, verify identity, and lock in the package name — it's permanent. Upload a signed bundle and confirm analysis (package, versionCode, permissions, SDKs) with the AAB analyzer before anything downstream. Wrong-build uploads poison every document generated after them.
Step 3–4: Data Safety and privacy policy, kept consistent
Generate the Data Safety profile, review every flagged row, then draft the privacy policy from the same profile and publish its URL. If your app has accounts, generate the deletion instructions from the same intake. Detail on each lives in the Data Safety guide and privacy requirements guide.
Step 5–6: Listing, screenshots, staged rollout
Write the listing with the listing generator, export screenshots with the screenshot generator, craft the required visuals with the app icon generator and feature graphic generator, then roll out internal → closed → production. Track every Google-side change in the policy changelog so "as of when?" always has an answer.
Frequently asked questions
How long does Google Play review take?
Typically a few days for new apps, sometimes hours for updates — but policy reviews and rejections reset the clock. Budget a week for a first submission and never promise users a launch date tied to approval.
How much does a Google Play developer account cost?
A one-time $25 registration fee paid to Google, separate from any tooling. It covers unlimited apps under one account.
Should I use internal, closed, or open testing first?
Internal testing for your own devices, closed testing for real-user feedback (Play may require a test cohort before production access for new accounts), then a staged production rollout. Each stage is a separate release with its own versionCode.
What causes most first-submission rejections?
Data Safety answers contradicting the binary, missing or dead privacy policy URLs, misleading listing claims, and missing target-audience/age declarations. The readiness checklist catches all four before you submit.
Keep going
Work the checklist, not the panic
Upload your AAB and leave with a launch plan.