guide
Publish to Google Play
The Play Console steps that sit between a finished Android build and a public release, including testing tracks and data safety.
Publishing to Google Play starts before the upload. You need a Play Console account in the name of the business that should own the listing, app signing enrolled, and a package name you are willing to keep forever. The package name is not a label you can casually change later. Pick it once, and do not include a code name you will regret.
The artifact Play wants for new apps is an Android App Bundle, not an old-style APK, except where a private distribution channel still requires one. Play App Signing should be on so Google can deliver the right split per device and so a lost upload key is recoverable through the console process. Guard the upload key anyway. Recovery is a delay, not a hobby.
Use the testing tracks in order. Internal testing is for the team. Closed testing is for a named group and, for brand-new personal developer accounts, Play has required a closed test with real testers before production. Read the current rule for your account type when you open the console, because those requirements have changed and a blog post from two years ago will mislead you. Open testing is a public beta. Production is the store.
The store listing needs a default language, a short description, a full description, an icon, a feature graphic, and phone screenshots. Tablet and Android TV screenshots are required only if you opt those form factors in. Do not opt in to form factors the app has not been designed for. A phone app declared as a TV app fails in ways that look like a policy mystery and are really a checkbox.
Data safety, ads declaration, content rating questionnaire, target audience, and news or financial declarations must match the binary. If a SDK collects identifiers, the form has to say so. If the app is not for children, do not tick the child-directed boxes because they looked like a growth idea. Those boxes add Families policy rules.
Release notes should say what changed in language a user can check. 'Bug fixes and performance improvements' on every build teaches people to ignore the notes. A staged rollout, even at a small percentage, gives you a chance to watch crashes before the listing is in front of everyone. Crash rate and ANR rate in the console are the signals to watch. This page does not quote a rate from our own releases.
A rejected release usually points at a policy URL. Fix the cited issue and resubmit. Arguing with the first email before you read the linked policy wastes a day. If the rejection is about a permission, remove the permission or justify it in the declaration and in the in-app prompt.
ClickMasters can prepare a Play release with the build. Bring the account owner, the package name if one exists, and the list of SDKs. The iOS hub covers the Apple side of the same product when you ship both.
Make a release checklist that a person who did not write the code can follow. It should name the Play Console account, the package name, the track you will use, the rollout percentage, and the location of the upload key. Attach the data safety form answers and the list of SDKs they were checked against. Attach the screenshot folder and the short description. Run the checklist on an internal track before you touch production, including a fresh install and an upgrade from the previous version if one exists. Upgrades are where migrations fail. A production rollout is then a smaller step instead of the first time the bundle, the form, and the listing meet each other. Keep the checklist in the repository so the next release does not depend on someone's memory.
Ask for a scoped plan
Send the flows, the platforms, and the systems the app must call. We will reply with what is in the first release and what should wait. This guide is not a quote and not a test report.
Contact ClickMastersRelated guides
- Android software development
How Android software is structured: Kotlin modules, Compose, networking, and the Play target SDK a release has to meet.
- Android TV app development
How Android TV apps differ from phone apps: D-pad focus, the ten-foot layout, and the Play TV review checks.
- iOS app development
How native iOS apps are planned in Swift and SwiftUI, what App Store review checks, and when iPhone-only is the right scope.
- Android app development
How native Android apps are built with Kotlin, how Play review works, and what to decide about devices, screens, and background work.
- Flutter and React Native
When a shared Flutter or React Native codebase fits, where native code still appears, and how to choose between them.
- Mobile app cost
What actually changes the cost of a mobile app, how to read a range, and what to send so an estimate can be scoped.