How to Publish an App on Google Play: AAB to Production

Before You Start: Prerequisites

Publishing requires a verified developer account, a release-ready build, and the listing and policy inputs shown in your Play Console. Prepare these items before you create the release:

Active Google Play developer account: personal or organization, owned by the person or company publishing the app. Use the account registration guide if setup is not complete.
Signed AAB file: Google Play uses the Android App Bundle to generate device-specific APKs.
Store listing assets: app icon, feature graphic, screenshots, title, and descriptions that meet the current preview asset requirements.
Privacy policy: a public URL and in-app link whose wording matches the app and its SDKs.
Release configuration: a target API level that meets the current Google Play requirement. The policy changes guide explains how to verify the active deadline.
Policy inputs: Data safety answers, content rating answers, target audience, ads status, app access instructions, and any declarations requested for the app category.

Build a dependency schedule

Estimate listing assets, declarations, reviewer access, signing, testing, and correction work separately. A newly created personal account in scope has a published minimum 14-day opt-in window before it can apply for production access; Google controls the later review time.

Step 1: Prepare Your AAB File

Google Play uses Android App Bundles for new apps so Play can generate optimized APKs for device configurations. Measure delivered size for the actual bundle and asset-delivery setup rather than assuming one universal reduction.

Building an AAB in Android Studio

In Android Studio, open Build > Generate Signed Bundle/APK > Android App Bundle. Store the keystore, credentials, and ownership notes in an access-controlled backup before uploading the bundle.

App Signing by Google Play

With Play App Signing, Google protects the app signing key and you sign future uploads with an upload key. The account owner can request an upload-key reset if that upload key is lost or compromised. Record who controls Play Console, the upload key, recovery material, and release approval.

Step 2: Create Your Store Listing

The store listing explains what the app does and gives users the visual evidence they need before installing. Check Google's current store listing guidance while preparing each field.

App Title (Up to 30 Characters)

Use the product name and, when it fits naturally, a short category cue. For example, "Acme: Budget Tracker" tells a new user more than "Acme" alone.

Short Description (Up to 80 Characters)

State the main use case in plain language. Do not repeat the title or make a claim the app cannot demonstrate.

Full Description (Up to 4,000 Characters)

Explain the core flows, useful constraints, and next action. Include relevant search terms where they describe real functionality. For measured listing work, see our ASO service.

Screenshots

Show the app's real interface, important states, and supported device types. Use the Google Play screenshot checklist to verify dimensions, file types, device coverage, and policy-sensitive captions.

Step 3: Complete the Data Safety Form

Your Data safety declarations must match the released app, backend behavior, and third-party SDKs. A mismatch can trigger review questions or policy enforcement. Inventory these areas before answering the form:

Data types collected: location, contacts, photos, files, identifiers, and any other declared categories.
Purpose of collection: app functionality, analytics, advertising, personalization, account management, or another applicable purpose.
Data sharing: which data leaves the developer's organization, who receives it, and why.
Security and user controls: encryption in transit, deletion requests, retention, and account deletion where applicable.

Third-party SDK behavior counts even when your own application code does not collect the data directly. Work through the Data safety form guide with the final dependency list and privacy policy beside you.

Step 4: Content Rating (IARC)

Complete the IARC questionnaire from the content users can actually reach, including user-generated content, purchases, gambling references, violence, language, and social features.

If the questionnaire does not match the app, correct the answers or the product before release. The content rating guide maps the questionnaire to an evidence review.

Step 5: Pricing and Distribution

Choose whether your app is free or paid. Important: once an app is published as free, it cannot be changed to paid. You can add in-app purchases to a free app at any time.

Select target countries. You can choose all countries or specific markets. Consider starting with key markets and expanding later. For multi-language support, see our localization service.

Step 6: Closed Testing

For personal developer accounts created after November 13, 2023, Google's published testing requirements include at least 12 opted-in testers for 14 continuous days before the account can apply for production access. Follow the notice shown in your own Play Console because account state controls the required path.

Upload the release candidate to the required track, keep the tester group opted in, collect useful test evidence, and fix blocking defects. The closed testing guide covers the opt-in window and production-access application.

Step 7: Production Release

When you're ready, navigate to Production > Create new release. Upload your AAB file (or promote from testing tracks). Add release notes describing what's new. Review the release summary and click "Start rollout to Production."

Use a staged rollout when you have enough active users and monitoring to detect regressions before full exposure. Choose rollout steps from risk, sample size, crash and ANR signals, backend capacity, and rollback readiness.

Review duration varies by account, app category, declarations, reviewer access, region, and follow-up requests. Do not commit a launch date that assumes Google's decision time.

Post-Launch Checklist

Monitor Android vitals against the current Play thresholds, release baseline, device segments, and product error budget
Respond to actionable reviews with a specific fix, workaround, or support route
Track keyword rankings and optimize your listing based on performance data
Plan the next update from user impact, defects, policy deadlines, dependencies, and product evidence
Submit to alternative stores where the audience and maintenance cost justify it; see our alternative store service
Set up Google Play Console alerts for policy changes, review responses, and performance drops

FAQ

How long until my app appears in search results?

After a production release, verify country availability and listing state in Play Console. Discovery and keyword visibility are separate outcomes that depend on relevance, quality, competition, and user response.

Can I update my app after publishing?

Yes. Upload a new AAB with an incremented version code and complete the release checks. Updates still pass through Google's review process, whose duration is not controlled by the publisher.

What if I want to unpublish my app?

You can unpublish from Play Console. Existing users can keep the installed app, while new users can no longer find or install it. A later release still has to satisfy the policies and review state that apply at that time.

Do I need a privacy policy for a free app with no data collection?

Google's User Data policy requires a privacy policy link in Play Console and within the app. Audit every included SDK before claiming that no data is collected or shared, then describe the observed behavior accurately.