The developer account takes twenty minutes to create and one decision inside it shapes your entire launch timeline. Getting that decision right first time saves weeks.
The cost
Registration is a one-time US$25 fee. There is no annual renewal, unlike Apple. One account can publish unlimited apps.
Personal vs organisation: the decision that matters
At sign-up you choose an account type. This is not a label — it changes what you must do before you can publish.
Personal account
- Verified against your government ID; your own name appears as the developer.
- If created after 13 November 2023, you must run a closed test — currently 12 testers opted in continuously for 14 days — and then apply for production access before you can release publicly.
- Fastest to set up. Right for individuals and side projects.
Organisation account
- Requires a D-U-N-S number (free from Dun & Bradstreet, but issuance can take days to weeks), a registered business name, address and website.
- Not subject to the closed testing requirement for production access.
- Your business name appears as the developer, which reads more credible on the listing.
You cannot switch types later without going through support, and it is not guaranteed. If you have a registered business, use the organisation account even for a small app — it skips the single biggest launch blocker.
Verification, and how to not get stuck
Google verifies identity before you can publish. You will provide a government ID, an address, and a phone number, and for organisations, business documentation.
Things that reliably cause delays:
- Name mismatch — the name on your ID must match what you typed, exactly. Middle names and initials count.
- Address mismatch — it must match a document you can produce.
- Blurry or cropped ID photos — all four corners visible, no glare.
- A D-U-N-S record whose details differ from what you entered. Check your D-U-N-S entry first and correct it there before applying.
Verification commonly takes a few days and can take longer. Start it before your app is finished, not after — it is pure waiting time you can overlap with development.
What to set up immediately after approval
- Two-factor authentication. A compromised developer account can mean losing published apps.
- A payments profile, if you will ever sell anything or run ads. Adding it later blocks releases at an awkward moment.
- Users and permissions — invite collaborators with scoped access rather than sharing one login.
- A backup of your keystore, somewhere that is not the laptop you develop on.
Policy things worth knowing on day one
- Google can terminate accounts for serious or repeated policy violations, and termination can extend to related accounts. Creating a second account to escape a suspension is itself a violation.
- Inactive apps can be removed. If you publish and abandon, expect the listing to go eventually.
- Your developer name is public. Pick one you are willing to have on every listing.
If you end up on a personal account and facing the closed testing requirement, the closed testing tracker keeps the count and the eligibility date straight — the clock starts when your twelfth tester opts in, not when you send the invites.
Fees, tester counts and verification requirements change. Confirm the current rules in Play Console Help before planning around specific numbers.