How to Launch Your App on Google Play: Production Rollout

Launching to production is the last checkpoint of a long pipeline: the release you roll out here is what millions of users can install. The mechanics are simple — create a release on the Production track, resolve errors, choose countries, start the rollout — but the checks leading in make the difference.

Before you create the release

Google requires your setup to be complete before the release can go out: the store listing set up, the App content page (data safety and the rest) prepared, and prices set. For personal accounts created after November 13, 2023, production access must already be granted.

Create the release

1. 1

   Open the Production track

   In Play Console, go to production (one of the tracks for creating a release) and select Create new release.

1. 1

   Resolve outstanding releases first

   Create new release stays disabled while you have outstanding releases — staged rollouts that haven't reached 100%, or drafts sitting in the publishing overview. Roll them out or discard them before proceeding.

1. 1

   Add your app bundle

   Attach the signed Android App Bundle and fill in the release details — notes, version, and what's new.

1. 1

   Move to review-through and confirm

   Next takes you to the review and confirm screen, where the Errors summary lives. Errors must be resolved before publishing; warnings can publish, but Google recommends fixing them first.

Choose your countries

Each track lets you target specific countries and regions. Rolling out your first production release publishes the app to all Google Play users in the countries you selected — availability management is per-track, and clean country choices early avoid support noise later.

Start the rollout

1. 1

   Start rollout

   Select Start rollout to publish the release for the selected audience. For a first production release this also publishes your app to the store.

1. 1

   Watch the review

   The release goes through Google's review before it's live. A rejected release takes you back to fixing policy or listing issues — review the feedback carefully before resubmitting.

1. 1

   Confirm the app is live

   Check the store listing from a clean account and device. Install from the listing, not from a test link, to confirm what users see.

After the launch

The Dashboard becomes your cockpit: installs, uninstalls, ratings, crashes, and insights over time. Updates to the live app go through the same review pipeline, so plan update cadence with review time in mind — and keep your test tracks alive for QA on the next version.