How to Publish an App on Google Play: A Step-by-Step Guide

Your Android app is built and tested. Now it needs to reach users through the Google Play Store. The process is well documented, but there are several forms, policies and testing requirements that catch first-time publishers out, especially if you have a new personal developer account.

This guide walks you through each step in order. Google updates its Play Console and policies regularly, so always check the current requirements in Play Console and the official Play Console Help pages before you submit.

Step 1: Create a Google Play developer account

Sign up for Google Play Console with a Google account you intend to keep long term, ideally one owned by your business rather than an individual employee.

• Registration fee: a one-time payment of US$25.
• Account type: choose a personal account if you are an individual developer, or an organisation account for a registered business. Organisation accounts typically need a D-U-N-S number and business documents.
• Identity verification: Google verifies the developer's identity and contact details. Verification can take a few days, so start early.

Use the account type that matches who really owns the app. Changing ownership later is possible through an app transfer, but it is easier to get this right from the start.

Step 2: Prepare your app build and app signing

New apps on Google Play must be uploaded as an Android App Bundle (.aab), not an APK. The bundle lets Google generate optimised downloads for each device.

1. Set the application ID (package name), such as com.yourcompany.appname. It is permanent and cannot be changed after publishing.
2. Meet the target API level requirement. Google requires new apps and updates to target a recent Android API level; check the current minimum before building.
3. Enrol in Play App Signing. This is required for new apps. Google holds the app signing key, and you sign uploads with a separate upload key.
4. Keep your upload key safe. Store the keystore file and passwords securely with backups. If the upload key is lost, it can be reset through Play Console, but it causes delays.
5. Set version code and version name, and increase the version code with every release.

Step 3: Create the store listing

In Play Console, create your app and fill in the main store listing. This is what users see, so it deserves care.

• App name: up to 30 characters.
• Short description: up to 80 characters, shown prominently on the listing.
• Full description: up to 4,000 characters. Explain clearly what the app does and who it is for; avoid keyword stuffing and misleading claims.
• App icon: 512 × 512 pixels.
• Feature graphic: 1024 × 500 pixels.
• Screenshots: at least two for phones, with more recommended, plus tablet screenshots if you support tablets.
• Category, contact email and website.

You can add translated listings, for example in Hindi, to reach more users across India.

Step 4: Complete the app content declarations

Under the App content section, Google asks a series of questions. All must be completed before you can publish.

Privacy policy

You need a publicly accessible privacy policy URL, hosted on your website, that explains what data the app collects, how it is used and shared, and how users can contact you or request deletion. Apps that let users create accounts must also provide a way to request account deletion.

Data safety form

Declare what user data your app collects and shares, including data collected by third-party SDKs such as analytics, ads, crash reporting and payments. Be accurate: the answers appear on your public listing, and mismatches with your app's real behaviour can lead to rejection or enforcement.

Content rating

Complete the IARC questionnaire honestly. It produces age ratings for different regions. An incorrect rating can lead to your app being suspended.

Other declarations

• Target audience and whether the app is designed for children.
• Whether the app contains ads.
• App access instructions and test login details if parts of the app are behind a login, so reviewers can check them.
• Declarations for sensitive permissions, such as location in the background, SMS or call logs, where applicable.

Step 5: Use testing tracks before production

Play Console offers several testing tracks:

• Internal testing: quick distribution to a small group of up to 100 testers, useful for your own team.
• Closed testing: a wider group of invited testers, managed by email lists or Google Groups.
• Open testing: anyone can join from the Play Store listing.

Important for new personal accounts: Google requires personal developer accounts created after 13 November 2023 to run a closed test with a minimum number of opted-in testers for at least 14 continuous days before applying for production access. At the time of writing that minimum is 12 testers; it was previously 20. Organisation accounts are not subject to this requirement. Check the current numbers in Play Console, as Google may change them.

Use the testing period properly: gather feedback, fix crashes reported in Android vitals and be ready to describe your testing when you apply for production.

Step 6: Submit for review and release

1. Create a production release and upload your signed app bundle.
2. Write release notes describing what is new.
3. Choose the countries and regions where the app will be available.
4. Set pricing. Note that a free app cannot later be changed to paid.
5. Send the changes for review.

Review times vary. Many apps are reviewed within a few days, but new developer accounts and apps in sensitive categories can take a week or longer. Plan your launch date with a buffer and avoid announcing a fixed date until the app is approved. You can choose managed publishing if you want to control exactly when approved changes go live.

Common reasons apps are rejected

• Missing or inaccurate privacy policy or data safety answers.
• Reviewers cannot log in because test credentials were not provided.
• Requesting sensitive permissions without a clear, core need.
• Misleading descriptions, screenshots or use of other brands' names and logos.
• Crashes, broken features or placeholder content.

Frequently asked questions

How much does it cost to publish an app on Google Play?

The Google Play developer registration fee is a one-time US$25. There is no yearly renewal. Google takes a service fee on paid apps and in-app purchases, at rates set in its current policies.

How long does Google Play review take?

It commonly takes from a few days up to a week, sometimes longer for new accounts or apps needing extra checks. Updates to established apps are often reviewed faster.

Do I need a website to publish an app?

You need somewhere public to host your privacy policy, and a website makes your developer profile more credible. A simple business website is usually enough.

Need help publishing your app?

If you would rather have experienced hands manage app signing, store listings, data safety forms and testing tracks, our team in Patna can help. We build and publish apps for clients across India and abroad, with a free consultation and fixed, itemised quotes.

Visit our Android and iOS app development page or contact us. If you are still budgeting, our guide to app development cost in India may help.