Free tool

Google Play launch checklist

Everything to prepare before your first release: store listing, policies, quality checks and rollout. Tick items off as you go, and print it for a team review.

Google Play launch checklist: the tool

0 of 28 done

Your progress is saved in this browser.

Before you start

Store listing

Policy and compliance

App quality

Release

How it works

Why a checklist helps

Most rejected first releases are not rejected because the app is bad. They are rejected because a requirement was missed: a privacy policy that cannot be opened, a Data safety form that does not match the app, or no way to delete an account. These are quick to fix once you know about them, and slow to discover through repeated review cycles.

This checklist reflects the compliance and release steps we complete for our own apps on Google Play, including Maya: Yoga for Beginners, Traffic Quiz and Matric Guru. It is organized in the order you will meet them: account setup, the store listing, policy and compliance, app quality and the release itself.

How to use it

Work from top to bottom and tick items as you finish them. Your progress is saved in your browser, so you can close the page and come back. Each item has a short note explaining why it matters, which is useful when you need to justify the work to a team member or client.

Use the Print button for a team review before your first submission. A printed or shared copy makes it easy to assign items and to confirm nothing was skipped.

The four areas that cause the most delays

  • Privacy policy and data safety. The policy has to be public, current and consistent with the Data safety form. If you use analytics, crash reporting or ads, say so.
  • Account deletion. If people can create an account, Google expects an in-app way to delete it and a public web page for deletion requests. Explain what is deleted and what is kept, in plain language.
  • Target API level. Check the current requirement in Play Console before you start the release build, not on the day you submit.
  • Testing requirements for new accounts. New developer accounts can face extra closed-testing steps before production access. Plan that time into your schedule.

What this checklist is not

Google updates its policies often, and the Play Console is the final authority on what applies to your app. Treat this checklist as a practical guide to the work, and confirm the current rules in Play Console and the official Google Play policy pages before you submit. If you would rather have a team handle compliance and submission, our Android development service includes the Play Store listing and submission.

FAQ

Questions, answered

It varies, from hours to several days, and is longer for new accounts and for apps that request sensitive permissions. Submit well before any launch date.

Almost every app handles some data, such as device identifiers through analytics or ads. If in doubt, publish a short, accurate policy. It is cheap insurance.

Yes, in this browser on this device. It is not sent anywhere. Use Print or take a screenshot if you want to share your progress.

Yes. The Starter App package includes the Play Store listing and submission, and larger packages add a store optimization pass.

In Play Console and in Google's Play policy pages. This checklist is a practical summary, not a replacement for them.
Reply within 1 business day

Tell us what you're building.

Send the problem, not a polished brief. We'll tell you what it actually takes to ship it: stack, timeline and cost, before you commit to anything.