Before any bundle is uploaded you need a developer account, and the choices you make in the first ten minutes — account type, developer name, contact email — are the hardest to change later. This guide is what we wish every first-time publisher read before paying the fee.
The fee and what it covers
US$25, paid once, non-refundable, for unlimited apps under one account. There is no annual renewal (unlike Apple's US$99 per year). Payment is by card through Google Payments; the account is tied to a Google account, so create or choose one you will keep — a work address you might lose access to is a bad anchor.
Personal or organisation?
| Personal | Organisation | |
|---|---|---|
| Who | An individual publishing under their own name (or a trading name they use) | A registered business, non-profit or institution |
| Verification | Government ID, and sometimes proof of address | D-U-N-S number, official business documents, a website and email at your domain |
| Closed testing before production | Required: 12 testers opted in for 14 continuous days | Not required |
| Public developer details | Your legal name, country, and an email; a physical address if you sell paid apps or in-app products | Business name, address, phone, email, website |
| Payments profile for paid apps | In your name | In the business name |
| Time to open | Usually days | Days to weeks (D-U-N-S issuance can take up to 30 days if you don't have one) |
If you have a registered business, use it. The 14-day closed test on personal accounts is the single biggest source of launch-date surprises, and business details are what users and reviewers expect to see next to a commercial app. A sole trader without registration is a personal account; that is fine, and you can still show a trading name as the developer name.
Verification, step by step
- Google account with two-step verification enabled — Play requires it.
- Developer profile: legal name exactly as on your ID or company registration. This is checked against the documents.
- Contact details: a phone number and an email you can verify immediately. The email is not public unless you make it the developer email later.
- Organisation only: D-U-N-S number (free from Dun & Bradstreet; apply early), registered address, an official document, and a website whose domain matches the email you use.
- Identity documents: uploaded via the console. Verification typically clears within a few days; mismatches between the name typed and the name on the document are the usual cause of delay.
Nothing can be published until verification completes, and the console tells you so on the dashboard.
Developer name, public email, address
- Developer name appears on every listing. It must not impersonate another brand or include misleading terms ("Official", "Google", "Verified"). You can change it, but changes are reviewed.
- Developer email is public. Use a role address (
support@), not your personal inbox. - Physical address is required — and shown publicly — if you offer paid apps or in-app purchases anywhere in the account. Free apps with no purchases don't trigger it. A registered office or a business PO box is acceptable; a home address is what many personal publishers end up showing, so decide consciously.
The closed-test rule for personal accounts
Since late 2023, new personal accounts cannot publish to production until they have run a closed test with at least 12 testers opted in continuously for 14 days, then applied for production access via a short questionnaire. It applies per account, not per app — once you have done it for your first app, later apps skip it. Recruit more than 12 (friends drop out and reset nothing but your patience), use a Google Group to manage them, and start the clock the day verification clears. The full mechanics are in the closed testing guide.
Account hygiene that prevents disasters
- Add a second owner or admin (Users and permissions) so a lost phone doesn't lock you out.
- Never share an account across unrelated businesses. Enforcement against one app affects the whole account, and Google links associated accounts.
- Never buy or borrow an account. Google terminates accounts it identifies as transferred outside its own transfer process, along with every app on them.
- Keep the payment method valid even for free apps; a lapsed payments profile can suspend publishing.
- Respond to policy emails within the stated window. Most account-level actions start as a warning with a deadline.
Transferring an app later
Apps can be moved between developer accounts through the console's transfer request (you need the target account's transaction ID). Plan for this if an agency is publishing on a client's behalf: publish from the client's account from day one, or expect a transfer later. Package names, ratings and installs move with the app; the developer name on the listing changes.