Google Play launch checklist: from account to rollout

Publishing on Google Play used to be quick: upload, fill in a form, go live. It still is simpler than many people fear, but new accounts now face a testing requirement that can add weeks if nobody plans for it. This Google Play launch checklist covers the account, the testing rules, the policy forms, the store listing and the release itself. Google changes its requirements often, so confirm each item in Play Console and the Play Console Help Center before you rely on it.

Set up the developer account

• Choose the account type. Google Play has personal and organisation developer accounts. An organisation account shows your company as the developer and needs company details, including a D-U-N-S number. A personal account is tied to an individual.
• Pay the registration fee. It is a one-time fee. Check the current amount when you sign up.
• Verify your identity. Google verifies developer identity and contact details. Use real, monitored contact information, because policy notices go there.
• Invite your team. Give your developers and agency their own access with the right permissions instead of sharing a login.

Start this early. Verification can take days, and you cannot test or publish until it is done.

Plan for closed testing on new personal accounts

This is the step that catches teams out. At the time of writing, personal developer accounts created after November 2023 must run a closed test before they can apply for production access. The current rule asks for at least 12 testers who stay opted in for at least 14 days in a row. Google has changed these numbers before, so check the current requirement in Play Console.

How to get through it without stress:

1. Recruit testers before the build is ready. Friends, early customers and your waitlist all count, as long as they have a Google account and an Android device.
2. Start the clock early. The 14 days begin only once enough testers have opted in, so a late invite delays everything.
3. Ask for real use. Google asks how you tested the app and what you changed as a result when you apply for production. Collect feedback and ship at least one update during the test.
4. Answer the production questions honestly. Describe your testers, what they found and how the app is ready.

Organisation accounts are not currently subject to this rule, which is one more reason companies should publish under an organisation account.

Prepare the build

• Upload an Android App Bundle (AAB). New apps must be published as AABs, not APKs. Google Play generates optimised APKs for each device from the bundle.
• Use Play App Signing. Google manages the app signing key, and you keep an upload key. Store the upload key safely and note who has access.
• Meet the target API level requirement. Google requires new apps and updates to target a recent Android API level, and raises the bar every year. Check the current deadline before your final build.
• Set the version code and name. Each upload needs a higher version code than the last one.
• Read the pre-launch report. Play Console runs your build on real devices and reports crashes, accessibility issues and security warnings. It is free, and it finds things.

Complete the policy forms

Play Console asks you to fill in several declarations under App content. Each one has to be accurate.

Form	What it covers
Privacy policy	A public URL, also linked inside the app
Data safety	What data the app collects and shares, why, whether it is encrypted in transit, and whether users can request deletion
App access	Instructions and a demo login if parts of the app are behind sign-in
Ads	Whether the app shows ads
Content rating	A questionnaire that produces age ratings for each region
Target audience	The age groups the app is for. Apps aimed at children face extra rules
Account deletion	If users can create accounts, a way to request deletion in the app and through a web link
Sensitive permissions	Declarations for permissions such as background location, SMS or all-files access

The data safety form is where most launches stall. List every SDK in the app, including analytics, crash reporting, ads and payments, and check what each one collects. The form must describe the app’s real behaviour, including those SDKs.

Build the store listing

Your listing is your shop window, and it is also reviewed against policy.

• App name, within Google’s character limit, with no misleading claims or emoji spam.
• Short description, one line that says what the app does.
• Full description, in plain language. Avoid keyword stuffing and unverifiable claims like “the best app”.
• App icon at the required size.
• Feature graphic, the banner shown at the top of your listing in some places.
• Phone screenshots, showing real screens. Add tablet screenshots if you support larger screens.
• Category, contact email and website.

Check the current image sizes and character limits in Play Console when you prepare the assets, because they appear right on the upload form.

Your Google Play launch checklist for release day

Before you press the button, run down this list:

• Closed test completed and production access approved (new personal accounts)
• AAB uploaded, signed and targeting the required API level
• Pre-launch report reviewed and crashes fixed
• All App content forms complete and accurate
• Store listing finished, with real screenshots
• Countries and pricing set
• Demo account working for reviewers
• Support inbox monitored

Then choose a staged rollout. You release the update to a small percentage of users first, watch crashes and reviews in Android vitals, and increase the share once it looks healthy. If something breaks, you can halt the rollout. For a first release you can also use managed publishing, so the approved app goes live only when you choose.

Google reviews new apps and updates, and the first review can take longer than later ones. Leave a buffer before any public launch date.

After launch

The listing and the app keep needing care. Watch Android vitals for crash and ANR rates, reply to reviews, keep the data safety form current when you add an SDK, and update the target API level each year. These are small jobs, but skipping them can get an app hidden or removed, so keep this Google Play launch checklist handy for every update. Our post on app maintenance cost after launch covers the ongoing budget.

At Batriders, store prep is part of every mobile build, from the listing and screenshots to review notes and testing on real devices. You can see how it fits into a project on our mobile app development page, and the iOS side is in the App Store submission checklist.

Frequently asked questions

Do I need 12 testers to publish on Google Play?

If you have a personal developer account created after November 2023, the current rule asks for a closed test with at least 12 opted-in testers for at least 14 days before production access. Organisation accounts are not currently subject to it. Check Play Console for the latest numbers.

Can I still upload an APK?

Not for new apps on Google Play. New apps must use the Android App Bundle format. APKs are still used for testing and distribution outside the store.

How long does Google Play review take?

It varies by app and account history. Many updates are reviewed within hours or a few days, while new apps and new accounts can take longer. Plan for a buffer.

What happens if my data safety form is wrong?

Google can reject an update, ask you to fix the form, or take further action if it does not match what the app does. Review it whenever you add or remove an SDK.

The testing rule feels like a hurdle, but two weeks of real users before launch tends to make a better app anyway.