How to publish an app on Google Play: step by step

Everything you need to prepare, in the order you will need it, from our experience publishing our own apps.

By Your Small AppPublished 21 November 20263 min read

Building the app is only part of the job. Google Play has its own checklist, and missing one item can delay a release by days. This is the order we follow. Google changes its rules from time to time, so check the Play Console for the latest requirements before you start.

1. Create a Google Play developer account

Sign up at the Google Play Console. There is a one-time registration fee of about 25 US dollars. You will need to verify your identity, and for a business account you will need business details. Do this first because verification can take a few days.

2. Prepare the app bundle

Google Play takes an Android App Bundle (an .aab file), not an APK. Sign it with an upload key. Back up your key and its passwords safely, because losing the upload key causes serious trouble for updates. Choose a final package name such as in.yourcompany.yourapp, because it cannot be changed after release.

3. Write the store listing

  • App name: up to 30 characters. Put the main search words in it.
  • Short description: up to 80 characters. This is the line people read first.
  • Full description: up to 4,000 characters. Say what the app does, list features, and write for real people, not only for search.

4. Make the graphics

  • App icon: 512 by 512 pixels
  • Feature graphic: 1024 by 500 pixels
  • Phone screenshots: at least two, ideally four to eight showing the real app

5. Publish a privacy policy

If your app collects any data, including through ads or analytics, you need a privacy policy on a public web page. Add the link to the listing. Make sure the policy matches what the app really does.

6. Complete the declarations

  • Data safety form: what data you collect and how it is used
  • Content rating: a short questionnaire
  • Target audience: whether the app is for children (extra rules apply)
  • Ads: declare if the app contains ads
  • App access: if sign-in is needed, give Google a test account

7. Run any required testing

Google asks some newer developer accounts to run a closed test with a minimum number of testers for a set number of days before they can publish to production. The numbers have changed over time, so check the Play Console. Plan for this, because it affects your launch date.

8. Submit for review

Upload the bundle to a production release, add release notes, and send it for review. Reviews often take from a few hours to a few days, longer for new accounts.

9. After you go live

  • Check the listing on a real phone
  • Reply to reviews, since it helps ranking and trust
  • Watch crashes in the Play Console and fix them quickly
  • Ship small updates regularly

Common mistakes

  • Leaving the privacy policy until the last day
  • Losing the signing key
  • Screenshots that do not match the real app
  • Asking for permissions the app does not need
  • Choosing a package name you later want to change

We have published several apps to Google Play and handle the listing, graphics, policy and release for our clients. Read about Android app development or start your app.