How to Publish Your First Android App on Google Play Console

Overview

This tutorial provides an end-to-end walkthrough on how to publish an Android application on Google Play Console. Starting from an existing developer account, the video details how to initialize an app, define its metadata, select its distribution model, and complete all mandatory Google Play policy declarations, including Privacy Policy, Data Safety, Content Rating questionnaires, and Target Audience specifications. Viewers are then guided through the Store Presence configuration, including setting app categories, tags, contact details, crafting optimized short and long descriptions, and uploading required visual assets such as icons, feature graphics, and phone screenshots. The tutorial also highlights generating content with AI tools to speed up the store listing workflow. Finally, the video covers generating a production-ready signed Android App Bundle (.aab) with a secure keystore using Android Studio. It demonstrates uploading the bundle to the Internal Testing track, configuring email test lists, setting up closed testing country tracks, and troubleshooting release warnings before submitting the app for Google Play review.

Introduction & Overview

00:00

Overview of the tutorial covering how to configure, sign, and submit an Android application to Google Play Console.

• Follows previous setup of a developer console account
• Outlines the workflow: policy setup, store listing, signing, and testing tracks

Creating an App Listing

00:34

Creating the app container within Google Play Console and defining initial parameters.

• Click 'Create app' on dashboard
• Specify App Name, default language, and type (App vs Game)
• Declare Free or Paid pricing model and accept Developer Policies

Policy Declarations: Privacy Policy, Ads & Access

01:21

Navigating to 'Policy and programs' > 'App content' using the sidebar to complete initial mandatory declarations.

• Provide a valid Privacy Policy URL
• Declare whether the app contains advertisements
• Specify App Access restrictions or credentials required by reviewers

Content Rating & Target Audience

02:04

Completing the official rating questionnaire and setting target age groups.

• Fill in developer contact email and app category
• Answer questions regarding user content sharing, online content, and downloads
• Define target age group (e.g., 13+ or 18+ to avoid strict Families policy overhead)

Data Safety, Advertising ID & Specific App Policies

03:16

Submitting details on user data collection, security practices, and device identifiers.

• Declare whether user data is collected or shared (encryption in transit, account creation requirements)
• Declare Advertising ID usage purpose (analytics vs marketing/advertising)
• Complete declarations for Government, Financial, and Health features

Store Settings, Tags & Developer Contact Details

05:46

Configuring how the app is organized and found by users in the Play Store.

• Select App Category (e.g., Tools) and assign up to 5 relevant tags (e.g., Productivity, Tools)
• Provide public contact email, optional phone number, and website

Main Store Listing & Graphic Assets

07:03

Entering metadata descriptions and uploading standard visual assets.

• Provide App Name, Short description (max 80 chars), and Full description (max 4000 chars)
• Optionally link a promotional YouTube video URL
• Upload 512x512 PNG app icon, 1024x500 feature graphic, and phone/tablet screenshots

Configuring Internal Testing & Tester Email Lists

10:14

Setting up the internal test track to distribute test builds to designated testers.

• Create an internal tester email list
• Add individual tester email addresses or import via CSV
• Save tester list and note join-link availability upon release creation

Building Signed Android App Bundle (.aab) in Android Studio

12:00

Generating a production-ready signed .aab package using Android Studio and creating a release keystore.

• Select 'Build' > 'Generate Signed Bundle / APK'
• Choose 'Android App Bundle' (.aab) format instead of legacy .apk
• Create a new Key Store (.jks), specify key alias, password, validity, and certificate details
• Build release variant bundle

Uploading App Bundle & Fixing Release Declarations

14:26

Uploading the generated .aab bundle to Play Console and clearing declaration errors.

• Drag and drop app-release.aab into App Bundles section
• Verify Target SDK, API levels, and supported device counts
• Update any conflicting Advertising ID declarations or release notes before proceeding

Setting Up Closed Testing & Preparing Review

16:06

Configuring target geographic regions and testers for the closed alpha track.

• Select countries/regions where the test track should be targeted
• Assign tester lists and feedback email addresses
• Save track configuration in preparation for review and production approval