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

Getting an Android app onto Google Play is more than uploading a file. You need a developer account, a correctly built app bundle, a complete store listing and several policy declarations. Skipping any of these causes delays or rejection. This walkthrough covers the process in order.

Google updates its requirements regularly, so treat this as a map and confirm the current details in the Play Console help pages as you go.

Step 1: Create a Google Play developer account

• Sign up at the Google Play Console with a Google account.
• Pay the one-time registration fee (check the current amount when you register).
• Choose personal or organisation account. Organisations typically need a verified business identity, such as a D-U-N-S number.
• Complete identity verification, which can take some days.

Use an account that the business will control long term. Moving an app between accounts later is possible but adds work.

Step 2: Prepare the app for release

Before building, confirm:

• A unique package name (application ID) that you will never change after publishing
• The app meets Google’s target API level requirement. New and updated apps must target a recent Android version, and the required level increases over time.
• You have removed test code, debug flags and sample credentials. See our mobile app security checklist.
• Performance and stability are acceptable on real devices. See app performance optimisation.

Step 3: Build a signed Android App Bundle

New apps are published as an Android App Bundle (.aab), which lets Google Play generate optimised downloads for each device.

• Build a release bundle, not a debug one.
• Enrol in Play App Signing, where Google holds the app signing key and you sign uploads with an upload key. Keep your upload key and its password safe and backed up.

Step 4: Create the app in Play Console

Choose Create app, then set the default language, app name, whether it is an app or game, and whether it is free or paid. Note that you cannot change a free app to paid later, so decide carefully.

Step 5: Complete the store listing

This is your sales page. Prepare:

• App name (up to 30 characters) and short description (up to 80 characters)
• Full description (up to 4,000 characters) written for readers, with relevant phrases used naturally
• Icon (512 × 512 px), feature graphic (1024 × 500 px) and screenshots
• Optional promo video
• Category and contact details, including an email address

Our guides to ASO, keyword research and screenshots that convert will help you write and design this well.

Step 6: Complete the App content declarations

Google requires several forms before release:

• Privacy policy URL
• App access: provide test credentials if parts of the app require login
• Ads declaration: whether the app contains ads
• Content rating questionnaire, answered honestly
• Target audience and content, including whether the app appeals to children, which triggers extra policy requirements
• Data safety section: what data the app and its SDKs collect, share and protect. Make sure it matches reality.
• Additional declarations depending on the app type, such as health, finance or news

Inaccurate declarations are a common cause of rejection or removal.

Step 7: Test before production

Use testing tracks:

• Internal testing: quick distribution to a small team
• Closed testing: invited testers
• Open testing: anyone can join

Newer personal developer accounts may be required to run a closed test with a minimum number of testers for a set period before applying for production access. Requirements change, so check the current rules early and build that time into your schedule.

Step 8: Release to production

Create a release, upload the bundle, add release notes and select countries. You can use a staged rollout, releasing to a percentage of users first and increasing if all looks healthy. Submit the release for review.

Review times vary, from hours to several days, and can be longer for new accounts. Keep an eye on the Play Console for messages.

Step 9: After launch

• Monitor crashes and ANRs (app not responding) in Android vitals
• Read and respond to reviews
• Track installs, retention and uninstalls (see improving retention)
• Plan regular updates, including meeting new target API requirements each year

Common reasons for rejection

• Inaccurate or missing data safety or privacy information
• Misleading metadata, such as irrelevant keywords or false claims
• Crashes or broken functionality at review time
• Missing login credentials for reviewers
• Violations of policies on user-generated content, permissions or ads

Checklist

• Developer account created and verified
• Package name final; target API level met
• Signed .aab built; Play App Signing enabled
• Store listing complete with graphics
• Privacy policy, content rating and data safety completed
• Test track requirements understood and met
• Release notes written; staged rollout planned
• Monitoring and update plan in place

Final thoughts

Publishing is easier when you treat it as a checklist rather than a surprise. Start the account and testing requirements early, answer policy forms accurately and plan for ongoing updates. For help shipping an Android app end to end, see our app development service or contact us. If you also target iPhone, read how to publish on the App Store.