Google Play Console is the account, the forms and the four tracks a release goes out on.

Opening a Google Play developer account

Registration is a payment, not a subscription. Google charges a US$25 one time registration fee, paid by credit or debit card at signup, and there is no annual renewal to forget. You have to be at least 18 years of age to sign up for a Play Console account.

The first real decision is the account type, and it is not cosmetic. A personal account is a person, and Google verifies your own legal name and address. An organization account is a registered business, and Google checks it against an external business registry instead. The two are verified differently and treated differently later, so pick the one that matches who is actually publishing rather than the one that is quicker to open.

During setup Google may ask for a valid government ID and a credit card, both under your legal name, and it warns that the registration fee is not refunded if the information you provide turns out to be invalid. Personal accounts created after November 13, 2023 also carry testing requirements before they can distribute an app, which is the gate covered further down this page.

Google Play Console Help, register for a Google Play Developer account

Identity verification, and the way it bites later

Verification is not a box you tick once at signup. Google asks you to verify your identity details before publishing on Google Play, and it keeps checking them afterwards. On a personal account those details are the legal name and address held on the Google payments profile linked to the account. On an organization account the check runs against a D-U-N-S number, and the organization details have to match the Dun and Bradstreet profile behind it.

Contact details get their own treatment. Email addresses and phone numbers on the account are verified with one time passwords, and they have to remain operational for the duration of your developer account. A phone number that belonged to a contractor at signup, or a shared inbox nobody reads, is a problem waiting for a bad week.

State the consequence plainly, because it is bigger than people expect. When Google finds a mismatch between the payments profile and the Dun and Bradstreet record it emails a deadline, and its own documentation says the account can be restricted if you miss it, which would remove all of your apps from Google Play. Verifying a payment method alone can take up to five days. This is work to finish before there is a launch date, not after.

Google Play Console Help, verify your developer identity and account information

Account level and app level: where each setting lives

Nearly every Play Console question of the form where is that is really a question about which level it belongs to. Account level covers the developer account details, the payments profile, users and permissions, and API access. App level covers the release tracks, the App content declarations, the store listing, and the crash reporting and statistics for one app. Open the console at the account home and you are looking at the first set. Select an app and the left hand navigation changes to the second.

Users and permissions follows the same split, and small teams get this wrong in a predictable way. There is one account owner, there are admins who can invite and remove people, and there are users with individual permissions. Account permissions apply to all apps in the developer account. App permissions apply only to the selected app. Permission groups exist so the same set can be handed to several people at once. A contractor who needs to push a test build does not need account level access, and granting it because it is faster is how someone ends up able to change your payout details.

App level is also where you find out why a tester is still on last week's build. What a device receives depends on the track it is opted into and how far a staged rollout has actually got, not on the moment you pressed start: auto update android app.

Play Console release tracks, and the gate on production

Four tracks run side by side and the same build is valid on any of them. Internal testing distributes to up to 100 testers per app and is the quickest way to get a build onto a real phone. Closed testing works from tester lists by email address, where you can create up to 200 lists and each list can hold up to 2,000 users. Open testing is available to anyone who opts in on Google Play, unlimited by default. Production is the public listing in the countries you select.

One rule catches people out on the fast track. A user who opts into your app's internal test is no longer eligible to receive an open or closed test for that app. If you also need to see what an outside tester sees, keep at least one phone off the internal list.

Production has a gate in front of it for newer accounts. Personal developer accounts created after November 13, 2023 have to run a closed test with a minimum of 12 testers who have been opted in continuously for at least 14 days, and then apply for production access on the Dashboard in Play Console. Testers who opt in, test for fewer than 14 days and then opt out do not count, and if someone opts back in later the 14 days have to be consecutive. Treat it as a date in the calendar rather than a checkbox: google play closed testing.

Nothing in Play Console compiles anything. Every track takes a file you already produced and signed, so the console is the second half of the job and the first half happens somewhere else entirely: building the binary first.