Google Play Console Guide: Accounts, Testing and Launch

The Google Play Console is Google's website for publishing Android apps. You create the app there, upload builds, run tests, fill in the policy declarations, write the store listing and release to production. For most owners the hard parts aren't technical. They're picking the right account type, getting through the identity checks and, for personal accounts, a closed testing rule that adds at least two weeks to a first launch.

We set up Play Console listings for clients as part of our mobile app service, and this guide follows the order we actually work in. For the Apple side, see our App Store Connect guide.

Should you open a personal or organization account?

Google's own rule is simple: "Choose a personal account if your account is for personal use," and "Choose an organization account if you're creating an account for an organization or business." If the app belongs to a company, go with organization.

An organization account needs a D-U-N-S number from Dun & Bradstreet, which Google says is free to request. Some apps must use an organization account no matter who builds them, including financial services, health apps, apps using the VpnService class and government apps. Both types have the same core features. The big practical difference is the testing rule for new personal accounts, covered below.

Signing up: the fee and identity checks

• An active Google Account, and you must be at least 18.
• The 25 USD one-time registration fee, paid by card. Google doesn't accept prepaid cards.
• Identity verification. You may be asked for a government ID and a credit card in your legal name. Google says the fee isn't refunded if your information is judged invalid.
• For personal accounts, proof that you have access to a real Android device, done through the Play Console mobile app before you can publish.

How do you give your developer access?

Invite them under Users and permissions. Only the account owner or an admin can invite people.

1. 1Open Users and permissions and click Invite new users.
2. 2Enter their email address. They'll need to sign in with a Google Account at that exact address.
3. 3Set an access expiry date if the work is a fixed project.
4. 4Choose app permissions for specific apps, or account permissions that apply to every app. Leave the admin toggle off unless they truly need full access.
5. 5Click Invite user.

The closed testing rule for new personal accounts

This is the step that surprises people. If your personal developer account was created after November 13, 2023, Google requires a closed test with "a minimum of 12 testers who have been opted in continuously for at least 14 days" before you can apply for production access. Google's FAQ adds that the 14 days must be consecutive.

A few practical notes:

• Testers join through an email list or a Google Group, then accept the opt-in link. Google says the link only shows once the app's status is Published, so get the test live before you send invites.
• Testers need to stay opted in. Someone who opts out partway through stops counting toward the continuous 14 days.
• Recruit more than 12. People drop out or never accept, so line up a few spares.
• Testers can send private feedback through Google Play, but they can't leave public reviews on test versions.

When the test is done, open the Dashboard and click Apply for production. The form has three parts: your closed test, your app and your production readiness. Google asks things like how easy it was to recruit testers, who the app is for and what you changed based on what you learned. Google says review "usually takes seven days or less, but can occasionally take longer." Specific answers about real feedback read much better than one-line replies.

Internal, closed and open testing

Play Console has three testing tracks. Internal testing is the quick one, for up to 100 testers per app, and it's ideal for letting the owner and staff try a build early. Closed testing is invite-only through email lists or Google Groups, and it's the track that counts for the 12 tester rule. Open testing lets anyone join from Google Play. If you've used TestFlight on iPhone, internal and closed testing fill the same role. Our TestFlight guide covers the Apple version.

The App content declarations

On the App content page, Google asks for a set of declarations. Plan to complete all of them before your first release:

• Privacy policy. Required for every app, even one that never touches sensitive data. It has to be a public web page, not a PDF or a download.
• Ads. Say whether the app shows ads, including ads from third-party SDKs. Apps with ads get a Contains ads label.
• App access. If any part of the app sits behind a login, give reviewers working credentials. You can add up to five sets of instructions, plus notes for one-time passwords or multi-factor sign-in.
• Target audience and content. Declare the age groups you target. Including children brings in the Families policy requirements.
• Content ratings. Fill in the questionnaire, and your answers decide the rating. Google warns that misrepresenting your content may lead to removal or suspension.
• Data safety. Google says even apps that collect no user data must complete this form, and that you're responsible for what any SDK in your app does.
• Permissions declaration. Only needed if your app asks for high-risk permissions such as SMS or Call Log.

Store listing basics

• App name, up to 30 characters.
• Short description, up to 80 characters.
• Full description, up to 4,000 characters.
• A 512 by 512 app icon and a 1024 by 500 feature graphic.
• Screenshots for phones and any other device types you support. Our screenshot size guide has the exact rules.

Google warns that repetitive or irrelevant keywords in these fields can get an app suspended, so write for people first. Our app store optimization guide shows how to make each field pull its weight.

Releasing to production

Once production access is approved, or straight away if the rule doesn't apply to your account, create a production release, upload your Android App Bundle, add release notes and send it for review. Give a brand-new account a few days of slack for that first review. After launch, updates go through the same release flow, and you can roll them out to a percentage of users first.

Want this off your plate? Our mobile team handles Play Console setup for clients: the declarations, the store listing, the screenshots, the closed test logistics and the production application. The account stays in your company's name the whole time. If your app started as a website, our guide to turning a website into an app covers what Google and Apple expect.

Roenic Natarelli

Founder, Virtual Horizons

Roenic runs Virtual Horizons and is a Base44 Legend Partner, Ambassador and Community Pillar, Base44 Shark Tank winner and multiple-time Vibe Sprint winner. The studio builds web and mobile apps, AI voice agents and automations, with more than 10 apps live on the App Store and Google Play. More about us