Publish to the Google Play Store

Heads up... You've reached locked video content where the transcript will be shown as obfuscated text.

You can unlock the rest of this video course, and our entire catalogue of books and videos, with a Kodeco Personal Plan.

Unlock now

In this episode, you will see how to create a production release. You will ideally do so for your app after fixing all the observations from testers from different testing tracks. Login into Google Play Console and click on the app for which you would like to create a production release. Before creating a production release, learn what is managed publishing. Click publishing overview in the left navigation panel. Click manage to the right of managed publishing status. With managed publishing, you can control when your updates to the app are published on Google play. You can turn managed publishing on or off at any time. If it is on, any changes that are in review won't go live until you decide. If it is off, any changes that are in review will go live as soon as they are approved. To know more about managed publishing, when you should use it and what kind of changes are held back by managed publishing, refer to the link in the resources for this episode. Keep managed publishing off for this app. Close the form, click production in the left navigation panel. There are three tabs, release dashboard, releases, countries and regions. In order to publish to production, you need to add at least one country from here. Click add countries or regions. You can make your app available to all countries by checking the checkbook next to country and region. Alternatively, search for a specific country. (keyboard clacking) See you can add only United States after searching it. Then click add countries and regions. Now go to releases tab and click on create new release. If this is disabled, you may have outstanding setup tasks to complete. This may be listed on the dashboard page. Now either upload app bundle from your local or click add from library. Here it will show all the bundles you have previously uploaded in any of the testing tracks. In our case, I select one we uploaded for internal testing, click add to release. You can update the release name, update the release notes or copy from any of the previous releases in any of the tracks. Click save. Click review release. And now when you click start rollout to production, the update status will change to in review. After Google reviews your app, you'll receive an email about whether it's approved or needs more work. If it's approved and managed publishing is off, it gets automatically published and you'll receive a notification email. If your app requires additional work, you will receive an email with specific information about what needs improvement. Address those issues and resubmit your app for review. The review duration depends on how many apps have recently been submitted for review and how many correction your app needs. It can take up to seven days or even longer in exceptional cases. One more key feature related to production releases is stage rollout. You can release an app update to production and testing tracks using staged rollout. With a staged rollout your updates reaches only a percentage of your users which you can increase over time. Staged rollout can only be used for app updates and not when publishing an app for the first time. You can learn more about staged rollout from this page, link for which is provided in the resources.