How to publish an app on Google Play: step by step
Open a Play Console account, create the app, complete the policy declarations, upload a signed app bundle, test it, write the listing, then roll out.
By Sohail Hussain21 November 20265 min read
To publish an app on Google Play you open a developer account in your company's name, create the app in Play Console, complete the policy declarations (privacy, data safety, content rating and reviewer access), upload an Android App Bundle that targets the API level Google requires, test it on internal or closed tracks, write the store listing, and roll the release out. As of October 2026 the account costs a one-time US$25. For an organisation account, the process from a finished app to live usually takes a few days to a week. A new personal account adds a compulsory 14-day closed test.
The steps below are the order we follow on our mobile app development projects, where the Android release usually goes out alongside the App Store launch.
How do you set up the developer account and the app?
Step 1: Create a Google Play developer account
Choose an organisation account if you are a business. It needs a D-U-N-S number whose legal name and address match your company's, and Google shows your legal name, address, developer email and phone on your store page. A personal account shows an individual's name, and personal accounts created after November 13, 2023 must pass a closed test before publishing (step 5).
Pay the registration fee described in Google's Play Console registration help, then verify your identity and contact details. Verification can take a few days. Once it is done, invite your developer as a user with the permissions they need. Keep ownership in the company's Google account, not a developer's personal one.
Step 2: Create the app in Play Console
Select "Create app" and enter the app name (up to 30 characters), default language, whether it is an app or a game, and whether it is free or paid. Choose carefully: a free app cannot later be changed to paid. You can still sell in-app products and subscriptions in a free app.
What declarations does Google require?
Step 3: Complete the app content declarations
Before any release can go to review, Play Console's "App content" section must be complete. It asks for:
- Privacy policy URL. Required for nearly every app. Our privacy policy generator gives you a starting draft for a lawyer to review.
- App access. Test login details for the reviewer, if any part of the app is behind sign-in.
- Ads. Whether the app shows ads.
- Content rating. A questionnaire that produces ratings for each region.
- Target audience. Age groups; selecting children brings the Families policies into play.
- Data safety. Every type of data the app and its SDKs collect or share, and why. This becomes the data safety section of your listing, and it must match what the app actually does.
- Account deletion. If users can create an account, you must offer deletion inside the app and on a web page that works without the app, under Google's account deletion requirements.
- Other declarations for news, government, financial and health features, and separate forms if the app uses sensitive permissions such as SMS, call logs, background location or broad photo access.
The sensitive permission forms are where Android launches most often stall. If the app can use the system photo picker instead of reading the whole photo library, do that, and skip the form.
How do you build and test the release?
Step 4: Build a signed Android App Bundle
New apps are uploaded as Android App Bundles (.aab), not APKs, and use Play App Signing: Google holds the key that signs the app users download, and you sign uploads with a separate upload key.
The bundle must target a recent Android API level. Under Google's target API level requirements, from August 31, 2026 new apps and updates must target Android 16 (API level 36), and existing apps must target at least Android 15 (API level 35) to stay available to new users on newer devices. Google raises this every August, so it belongs in your maintenance calendar.
Step 5: Test on internal and closed tracks
Upload the first bundle to the internal testing track. Up to 100 testers you name can install it from Google Play, usually soon after upload and without waiting for the full review. Use it for two to four weeks of real use by your own team.
Each upload to a testing track also produces a pre-launch report: Google installs the app on a range of real devices, crawls it and reports crashes, accessibility issues and security warnings. Read it before every release.
For a personal account created after November 13, 2023, Google's testing requirements apply: run a closed test with at least 12 testers opted in continuously for at least 14 days, then apply for production access. A tester who leaves and rejoins restarts their count. Organisation accounts skip this step.
How do you publish and roll out?
Step 6: Write the store listing
The main store listing needs:
| Item | Requirement as of October 2026 |
|---|---|
| App name | Up to 30 characters |
| Short description | Up to 80 characters |
| Full description | Up to 4,000 characters |
| App icon | 512 by 512 pixels, 32-bit PNG, up to 1 MB |
| Feature graphic | 1024 by 500 pixels, JPEG or 24-bit PNG, required |
| Screenshots | At least two in total; up to eight per device type |
Our app icon generator produces the 512-pixel Play icon along with the launcher and iOS sizes from one image. Write the short description as the one sentence that would make a stranger tap install; it is the only text most people read.
Step 7: Create the production release and roll it out
In the Production section, create a release, add the bundle and release notes, choose countries, and send it for review. Reviews usually finish within hours to a few days, though Google warns that some take a week or longer. You can choose to publish automatically on approval or use managed publishing to release at a time you pick.
For updates, use a staged rollout: release to a small percentage of users, watch crash and ANR rates in Android vitals, then increase. You can halt a staged rollout if something breaks, which is far better than a one-star wave.
After launch, Android vitals and user reviews tell you what to fix first. The ongoing work, from the yearly target API deadline to policy updates, is covered in app maintenance: what it involves and costs, and the mobile app development guide shows where the store launch sits in the whole project.
Was this guide useful?