How to Publish an Android App on Google Play: Beginner’s Guide

Building a high-quality Android application is a major accomplishment, but distributing it to millions of users worldwide through the Google Play Store is an equally critical engineering milestone. Over the past few years, Google has significantly updated its publishing standards, introducing strict 20-tester closed testing rules for personal developer accounts, mandatory Data Safety declarations, and target API level deadlines.

If you are releasing your first app, navigating the Google Play Console can feel overwhelming. This step-by-step guide walks you through the entire deployment pipeline—from creating a signed production bundle to passing automated security reviews and launching live.

Phase 1: Preparing Your Production Build (AAB & Keystore)

Gone are the days of uploading raw .apk files. Google Play requires the Android App Bundle (.aab) format. App Bundles allow Google Play to generate and serve optimized APKs tailored to each user’s specific screen density and CPU architecture, keeping download sizes small.

1. Generate a Secure Release Keystore

In Android Studio, navigate to Build > Generate Signed Bundle / APK > Android App Bundle. Create a dedicated release keystore file (.jks). Store this keystore file and its passwords in a secure password manager and off-site backup. If you lose your keystore and have not opted into Google Play App Signing, you will never be able to update your application again.

2. Enable Google Play App Signing

Google Play App Signing lets Google manage your app signing key securely on their infrastructure. If your upload key is ever compromised or lost, Google support can reset your upload key without forcing you to publish an entirely new app package.

Phase 2: Setting Up the Google Play Console Listing

To publish apps, you need a Google Play Developer Account ($25 one-time registration fee). Once logged into the Play Console, click Create App and configure your core metadata:

• App Name: Up to 30 characters. Make it clear and memorable (e.g., TaskMaster: Daily Habit Planner).
• Default Language & Category: Choose the primary language and whether it is a Game or Application.
• Free or Paid: Note that once an app is set to “Free”, you cannot change it to a paid download later (monetization must then be handled via In-App Purchases).

Phase 3: Store Listing Visuals & Conversion Optimization

Your store listing is your primary sales page. High-converting store listings include three essential creative assets:

Asset	Technical Specifications	Best Practice Advice
App Icon	512 x 512 px, 32-bit PNG, up to 1 MB.	Keep it clean, high contrast, avoiding cluttered text inside the icon.
Feature Graphic	1024 x 500 px, JPG or 24-bit PNG.	Showcases the primary brand mood and value proposition across search highlights.
Screenshots	Min 2, Max 8 per form factor (Phone, 7″ & 10″ Tablet).	Add descriptive headline banners above real device mockups highlighting core features.

Phase 4: Policy Declarations & Data Safety Form

Google’s automated review bots enforce strict policy verification. Missing or inaccurate policy declarations are the #1 cause of submission rejections.

1. Privacy Policy URL: You MUST host a publicly accessible, detailed privacy policy. For example, examine our TaskMaster Privacy Policy or our PhotoEditor Pro Policy to see compliant formats covering data collection, third-party SDKs, and user deletion rights.
2. Data Safety Section: Disclose whether your app collects location, personal information, financial data, or diagnostics, and whether that data is encrypted in transit or shared with ad networks.
3. Content Rating Questionnaire: Complete the IARC questionnaire accurately regarding violence, offensive language, or user-generated content.
4. Target Audience & Ads Declaration: Declare whether your app contains ads and whether it targets children under 13 (which triggers COPPA compliance).

Phase 5: The 20-Tester Closed Testing Requirement

For all personal developer accounts created after November 2023, Google mandates that you run a Closed Testing Track with at least 20 opted-in testers for a minimum of 14 continuous days before you can request access to Production publishing.

Google Play Publishing Checklist

• [ ] Release keystore safely generated and backed up.
• [ ] Android App Bundle (.aab) compiled in Release mode with ProGuard/R8 enabled.
• [ ] Target SDK level matches latest Google Play requirement (Android 14+).
• [ ] App Icon (512×512) and Feature Graphic (1024×500) uploaded.
• [ ] Minimum 4 high-resolution screenshots uploaded per supported form factor.
• [ ] Public Privacy Policy URL linked in Store Listing settings.
• [ ] Data Safety section completed matching exact SDK behavior.
• [ ] 14-day closed testing period completed with 20 active testers.

Frequently Asked Questions

How long does Google Play review take for new apps?

For new developer accounts, the initial review typically takes between 3 to 7 business days. Subsequent update reviews are usually processed within 24 to 48 hours.

What are the most common reasons for app rejection?

Discrepancies between your Data Safety declarations and embedded SDK code, broken login credentials provided for review testers, missing or non-compliant Privacy Policy links, and intellectual property copyright issues.

Can I update my app after it is published?

Yes. You simply bump the versionCode and versionName in your build.gradle.kts file, build a new signed .aab, and create a new release in the Production track of your Play Console.