How to Publish an App on Google Play: From APK to Live

Before You Start: Prerequisites

Publishing an app on Google Play requires a verified developer account and a release-ready app. Before diving into the publishing process, ensure you have these essentials ready:

• Active Google Play Developer Account — Either personal or organization (registration guide)
• Signed AAB file — Android App Bundle (preferred over APK since August 2021)
• App icon — 512x512 PNG with no alpha/transparency
• Feature graphic — 1024x500 JPG or PNG
• Screenshots — Minimum 2 (recommended 4-8) per device type, JPEG or PNG
• Privacy policy URL — Hosted on a public, accessible URL (not Google Docs)
• Short description — Up to 80 characters
• Full description — Up to 4,000 characters

Step 1: Prepare Your AAB File

Since August 2021, Google requires new apps to use the Android App Bundle (AAB) format instead of APK. AAB allows Google to generate optimized APKs for each device configuration, reducing download size by an average of 15%.

Building an AAB in Android Studio

In Android Studio: Build > Generate Signed Bundle/APK > Android App Bundle. You'll need a signing key (keystore). If this is your first app, Android Studio will help you create one. Keep your signing key safe — if you lose it, you cannot update your app.

App Signing by Google Play

Google Play App Signing is now mandatory for new apps. When you upload your first AAB, Google generates an app signing key managed by Google, and your upload key (the one you use to sign the AAB) is used only for authentication. This provides better security and enables features like dynamic delivery.

Step 2: Create Your Store Listing

Your store listing is what users see before downloading. It directly impacts your conversion rate and discoverability.

App Title (Up to 30 Characters)

Include your brand name and one primary keyword. Example: "Acme — Budget Tracker" is better than just "Acme" because it tells Google and users what the app does.

Short Description (Up to 80 Characters)

Your elevator pitch. Front-load the most compelling benefit. Example: "Track expenses, set budgets, and save money with smart insights."

Full Description (Up to 4,000 Characters)

Structure it with feature highlights, key benefits, and a call-to-action. Use the first 2-3 sentences strategically — they appear in search results. Include relevant keywords naturally, not stuffed. For professional optimization, see our ASO service.

Screenshots

Google requires at least 2 screenshots but recommends 4-8. Best practices: show real app screens (not mockups), highlight key features, add captions explaining the benefit, and include both phone and tablet screenshots if your app supports tablets.

Step 3: Complete the Data Safety Form

The Data Safety section is one of the most critical parts of your listing. Inaccurate declarations are the #1 rejection reason in 2025-2026. You must accurately declare:

• Data types collected — Location, contacts, photos, files, identifiers, etc.
• Purpose of collection — Analytics, advertising, personalization, core functionality
• Data sharing — Which data is shared with third parties and why
• Security practices — Encryption in transit, data deletion options

Remember: third-party SDKs count. If you use Firebase Analytics, Google Ads SDK, or any analytics/ad library, you must declare the data they collect even if your own code doesn't collect it directly.

Step 4: Content Rating (IARC)

Complete the International Age Rating Coalition (IARC) questionnaire. Answer honestly about your app's content: violence, sexual content, language, gambling, in-app purchases, user-generated content. Google automatically assigns age ratings based on your answers.

If your content doesn't match the assigned rating (e.g., you say no violence but the app includes combat), Google will reject your submission and may issue a policy strike.

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

If your account is new and personal, you must complete the 12-tester closed testing requirement before accessing production release. Even if you're exempt, closed testing is a best practice for catching issues before going live.

Upload your AAB to the closed testing track, invite testers via Google Groups, and monitor the test period. For established accounts, you can skip directly to production release, but we recommend at least a small internal test first.

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."

Google recommends staged rollouts for established apps: start at 5-10% of users, monitor crash rates and reviews, then increase to 25%, 50%, and finally 100%. For new apps, full rollout is typical.

Google's review typically takes 1-7 business days for new apps and a few hours to 3 days for updates. Complex apps (finance, health, children) may take longer.

Post-Launch Checklist

• Monitor crash rates in Android Vitals — aim for under 1.09% crash rate
• Respond to user reviews within 24-48 hours — this impacts your store ranking
• Track keyword rankings and optimize your listing based on performance data
• Plan your first update — regular updates signal an active developer to Google
• Submit to alternative stores for wider reach — 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 production release approval, your app is typically discoverable within 24-48 hours. However, ranking for specific keywords takes weeks to months and depends on your ASO strategy, reviews, and download velocity.

Can I update my app after publishing?

Yes. Upload a new AAB with an incremented version code. Updates go through the same review process but are typically approved faster (hours to 1-2 days).

What if I want to unpublish my app?

You can unpublish at any time from the Play Console. Existing users keep the app, but new users cannot find or download it. You can republish later without going through the full review process again.

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

Yes. Google requires a privacy policy for all apps, even if you don't collect any user data. Your policy should state that explicitly: "This app does not collect, store, or share any personal data."