HomeKnowledge BaseAndroid Publishing
Android

How to Publish Your App on Android (Google Play Store)

Publishing on Android is faster and more flexible. This guide walks through account setup, app listing, content declarations, AAB upload, and getting to the Play Store in days.

4 min read7 stepsUpdated Mar 2026
01

Create Google Play Developer Account

To publish on Google Play you need a Google Play Developer account. The one-time registration fee is $25 USD — much lower than Apple's annual fee — and setup takes about 30 minutes.

  1. 1Go to play.google.com/console and sign in with a Google account
  2. 2Accept the Developer Distribution Agreement
  3. 3Pay the one-time $25 registration fee via Google Wallet
  4. 4Complete your developer profile (name, email, phone number)
  5. 5Verify your identity — Google may request a government-issued ID
  6. 6Your account is typically active within a few hours
Tip: Use a dedicated Google account for your business, not a personal Gmail. This keeps your Play Console separate from personal apps and services.
02

Create Your App in Play Console

Once your account is active, create an app record in the Play Console. This is the container for all your app's versions, listings, and settings.

  1. 1In Play Console, click 'Create app'
  2. 2Enter your app name and select the default language
  3. 3Choose whether it's an App or a Game
  4. 4Select Free or Paid (note: you can change free → paid later, but not paid → free)
  5. 5Accept the declarations regarding content guidelines and US export laws
  6. 6Click 'Create app' — your app dashboard is now ready
03

Build & Sign Your AAB

Google Play requires apps to be uploaded as an Android App Bundle (.aab) — not a traditional APK. AABs are smaller and more efficient because Google Play generates optimised APKs for each device automatically.

Android App Bundle (AAB)

The required format for Play Store uploads since August 2021. Smaller download size for users, as Google serves device-optimised builds.

Upload Key vs App Signing Key

Google Play App Signing stores your actual signing key. You upload with an upload key. This protects your app if your key is ever compromised.

Version Code & Name

versionCode is an integer that must increment with every upload. versionName is the user-visible version string (e.g. 1.0.2).

Target SDK Version

Must target the latest or second-latest Android API level to remain on the Play Store. Google enforces this for new uploads and updates.

MobiDrag handles this automatically. When you export your app from MobiDrag, we generate a properly signed AAB with the correct version codes, target SDK, and app signing configuration.
04

Complete Store Listing

Your Google Play listing is the first touchpoint for most users. A well-optimised listing directly impacts your conversion rate and visibility in search results.

REQ

App Name

Up to 30 characters. Include your most important keyword naturally.

REQ

Short Description

Up to 80 characters. Shown on search results. Make every word count.

REQ

Full Description

Up to 4,000 characters. Use bullet points. Front-load your key benefits. Include relevant keywords organically.

REQ

Screenshots

At least 2 required for phone. Google allows portrait or landscape. Use annotated, lifestyle-style screens for best conversion.

REQ

Feature Graphic

1024×500px banner. Shown at the top of your listing when you have a promo video.

OPT

Promo Video

Optional YouTube URL. Autoplay when users visit your listing. Great for showing app flow.

REQ

Privacy Policy URL

Required for all apps. Must be publicly accessible and cover all data your app collects.

05

Content Ratings & Declarations

Google Play requires you to complete several declarations about your app's content and data practices. These affect your app's rating, target audience, and compliance with store policies.

🎮

Content Rating Questionnaire

Fill out the IARC rating questionnaire honestly. Your answers determine the age rating shown on your listing. False answers can lead to removal.

🎯

Target Audience & Content

If your app targets children (under 13), it must comply with Google's Families Policy and COPPA. You cannot use most ad networks or analytics tools.

📊

Data Safety Section

Declare what data your app collects, whether it's shared with third parties, and if users can request deletion. This is now prominently shown on listings.

📍

Permissions Declaration

If your app requests sensitive permissions (location, camera, contacts), explain why in the Play Console. Unjustified permissions can cause rejection.

06

Submit for Review

Once all sections are complete and your AAB is uploaded, you can submit your app for review. Android review is typically much faster than iOS.

  1. 1Go to 'Production' track in the Play Console → create a new release
  2. 2Upload your signed AAB file
  3. 3Add release notes (what's new) in all supported languages
  4. 4Review the 'Pre-launch report' — Google runs automated tests on real devices
  5. 5Confirm all policy declarations are complete (no yellow warnings)
  6. 6Click 'Review release' then 'Start rollout to Production'
Review timelines: For new apps, initial review takes 3–7 days. Updates to existing apps are usually reviewed within hours to 1 day. New developer accounts may experience longer initial review times.
07

After Approval

Your app is live on Google Play — but the work doesn't stop here. Here's how to make the most of your new listing.

Use Staged Rollouts

Don't release to 100% of users immediately. Start with 10–20%, monitor for crashes, then increase. This limits the blast radius of any bugs.

Android Vitals

Monitor crash rates, ANR rates, and battery usage in the Play Console. Google can reduce your visibility if your app has poor vitals.

Reply to Reviews

Google Play shows when developers reply to reviews. Active engagement improves your store ranking and user trust.

Use Custom Store Listings

Create different store listings for different countries or acquisition channels. Test different screenshots and descriptions.

What's next? Check our Timeline guide to understand the full publishing timeline on both platforms, or review our Compliance guide to ensure you meet all requirements.