Publishing a game on Google Play solo is a lot more paperwork than it used to be. If you’re picturing “build a game, hit upload, done,” the 2026 version of Google Play Console will catch you off guard: there’s a one-time developer fee, identity verification, a mandatory closed testing phase with real outside testers, and a separate developer verification process layered on top of all that. None of it is hard exactly, but it’s slow, and a few of the steps can quietly stall a solo release for weeks if you don’t plan for them.
I’ve gone through this process on two separate titles, and the biggest lesson both times was the same: the technical part of shipping a mobile game is rarely what eats your time. It’s Google’s account and policy machinery around it.
Quick answer: what it actually takes to publish on Google Play solo
As of late 2026, a solo developer needs a Google Play Console account ($25 one-time registration fee), a verified identity (government ID plus a credit card under your legal name), and — if your personal account was created after November 13, 2023 — a closed test with at least 12 opted-in testers running continuously for 14 days before you can apply for production access. On top of that, Google has been rolling out mandatory developer verification for anyone distributing Android apps, which asks for additional identity documents separate from the Play Console signup. Budget weeks, not days, for your first release.
Background: how the Google Play publishing process actually works
The process breaks down into a handful of stages, and they’re mostly sequential, so a delay early on pushes everything back.
- Create a developer account. You pick personal or organization, pay the $25 fee, and accept the Developer Distribution Agreement. You need to be 18 or older.
- Verify your identity. Google asks for a valid government ID and a credit card, both matching your legal name. Personal accounts created after early 2024 also have to confirm they have access to a real Android device through the Play Console mobile app.
- Set up your app listing. Store listing text, screenshots, content rating questionnaire, data safety form, target audience, privacy policy link. This part is genuinely within your control and can be done in an afternoon.
- Run a closed test. If your account falls under the newer personal-account rules, you need a minimum of 12 testers who opt in and stay opted in continuously for 14 days before you’re even eligible to apply for production (full public) access. Google reduced this from the original 20-tester requirement in December 2024, but 14 days is still 14 days you have to plan around.
- Apply for production access. Hitting the 12-tester/14-day mark doesn’t auto-approve you. Google also looks at tester engagement and reviews your answers about how the test went before granting full release.
- Developer verification. Separately from account setup, Google has been phasing in a broader Android developer verification requirement tied to distributing apps at all, which can mean additional document checks depending on your account type and region.
For a solo dev, step 4 is usually the bottleneck. Finding 12 real people willing to install your unfinished game and keep it installed for two straight weeks is harder than it sounds when you don’t already have an audience.
As a developer, here’s what actually caught me off guard
[TONAY: add your own experience here — e.g. how you found your 12+ closed testers, whether the identity verification step was quick or a hassle, how long your own review/approval actually took]
[TONAY: add your own experience here — any specific rejection, policy flag, or resubmission you had to deal with on either of your two games]
[TONAY: add your own experience here — one practical tip you’d give another solo dev trying to publish their first game on Google Play today]
What this means for players
None of this is really visible from the player’s side, but it explains a few things you’ve probably noticed. Smaller studios and solo devs increasingly soft-launch or run limited regional betas before a wide release — that’s partly the closed testing requirement in action, not just marketing strategy. It’s also part of why some promising-looking indie mobile games sit in “coming soon” limbo for months: the dev might be done building and still waiting on testers, review, or verification. And it’s one more reason genuinely scammy or copycat apps are a bit rarer on Google Play than they used to be — identity verification raises the cost of throwing up a throwaway app to basically zero return.
FAQ
Do I need a company to publish a game on Google Play?
No. A personal developer account is enough for a solo release — you just pay the $25 fee and verify your own identity instead of a business’s.
How long does the whole process take for a first-time solo developer?
Realistically, plan for at least 3-4 weeks end to end once you include the 14-day closed test, finding testers, and review time — longer if your identity verification or app review needs a second pass.
Can I skip the closed testing requirement?
Only if your personal account predates November 13, 2023, or you’re publishing under an organization account — otherwise the 12-tester, 14-day closed test applies before you can request production access.
Have you published a game on Google Play solo? What part of the process actually slowed you down? Let us know in the comments.
Source(s): Google Play Console Help: Get started with Play Console, PrimeTestLab: Google Play 20 to 12 Testers (2026 Closed Testing Rule)
Related: How Mobile Game Gift Codes Work (A Developer Explains) · [LINK: a drgamez article on a recently launched indie/mobile game]
While developing games, I learned about software architecture, managing debugging processes, and the procedures involved in launching a game.
