The first task asks only for a URL to your privacy policy. If you require it and have one viewable online, add the URL to it, click on Save in the bottom right corner and move onto the next item.

This too asks only one thing, this time relating to the ability to use the entirety of the app with a single device, irrespective of location and without signups or subscriptions. Check the appropriate box, save (bottom right corner as before) and continue.

The last of the single-question sections for a while. Simply declare whether or not your app contains ads, save and move to the next item on the list.

This section could be more involved, however if your app is for ages 13+, it will be a substantially shorter task. If not, you will be asked to confirm certain matters of compliance with GDPR, COPPA, etc.

This section will first ask you to place the app in one of three types of app (Game, Social/Comms, Misc.)

And then it will ask about the nature of the app in much greater detail.

When all of these questions are answered, the final page of this section will produce a series of age ratings for your app. Save and continue.

This section covers collection and handling of user data. If your app does not do this, the only thing you will need to cover is the single question shown below. If that is not the case, the below will rapidly expand and ask much more about what it is you are collecting from the user and where a user needs to go to request that data.

Until otherwise stated, it is assumed by Google that you are not developing a government app. If you are developing such an app, this lesson can not assist in any matters arising from disclosing that fact to Google.

If your app does with something with money beyond simple in-app purchases, this is the section that asks for you to declare what things of that nature that the app does.

Next, you are asked to disclose the ways in which the app has health features.

Moving onto the organisation and presentation section of the task track, you will be asked to enter some information germane to how the app should be found in store and how users can reach you regarding the app. Use the Edit links marked to bring up dialogs to change these settings.

Lastly on the setup track is the store listing. On top of the name and descriptions of the app, it requires at minimum the following images:

• A 512x512 app icon, no larger than 1MB filesize
• A 1024x500 feature graphic, no larger than 15MB filesize
• Two 16:9 and/or 9:16 screenshots from a phone, no larger than 8MB filesize each, no dimension smaller than 320 pixels nor larger than 3840 pixels.
• Two screenshots from a 7-inch tablet, with the same size specifications as the phone screenshots.
• Two screenshots from a 10-inch tablet, with the same filesize limit but the dimensions instead having to be between 1080 and 7680 pixels.

Here, you are choosing all countries/regions in which your app will be available. First, click on Add countries/regions, marked below

Next, check all of the countries you wish to release in. To save time, the topmost checkbox will select all countries.

Then click on Save in the bottom-most corner.

Depending on whether you have chosen Open Testing or another test, this screen will appear differently.

It is finally time to upload the app bundle. If you have created a release in the past for testing reasons and it passed review, you may use that release for the purposes of production.

This is screen is one that you will become the most familiar with as you test and release new builds on the platform. First, drag the .aab file that you built at the beginning of this lesson into the appropriate part of the page. While it is uploading and being briefly scanned, enter some details about the new release, giving a name for it and its release notes. (Take note of the markdown to indicate language - this is placed by default.) Once this is all done and there is nothing immediately wrong with the upload (a common pitfall will be uploading a new build where the build number hadn't been incremented in standalone settings beforehand), click on Next.

If there are no errors, you will now be asked to confirm the release on the next screen. If everything is as you want it, click on Save.

Finally, on this last screen you are shown an overview of your proposed release. Click on the button indicated to proceed.

Your app should now be submitted for review to production or the testing track of your choice and you may proceed further when it is determined to have met their criteria.