Google blocked my app for 3 months over Closed Testing. The honest guide I wish I'd had

A few months ago I finished my first Android app. Ready, uploaded, done. And Google said: you can't publish it until 12 people test it for 14 straight days.

Just like that. Welcome to mandatory Closed Testing.

What Google actually requires

If you create a new developer account, before publishing to production you need:

• At least 12 testers (real Google accounts).
• Them joining your testing group (a Google Group or email list).
• The app installed and in use for 14 consecutive days.

Only then can you request production access. If testers drop off on day 10 and you fall below 12, it gets messy.

Why it's a headache

Nobody has 12 friends willing to install your half-finished app and open it every day for two weeks. I didn't. And asking family is awkward (half forget by day three).

That's when the temptation shows up: "20 guaranteed testers for $5." Spoiler: they're bots or account farms. Google detects them and can ban your entire developer account. Not worth it.

The real options

1. Cross-testing: you test another dev's app and others test yours. Free, but takes time.
2. Real paid testers: real people who test your app for a small reward. Costs a bit, but they deliver.
3. Begging acquaintances: free, unreliable, doesn't scale.

What I ended up doing

I built TesterSplay because I got tired of this exact problem. The idea: a place where devs like me find real testers (not bots) who commit to the 14 days, with proof of activity so they don't leave you hanging.

If you're in the same spot, here's what matters: don't use bots. Get real humans, even if fewer. Google rewards genuine use and your account stays safe.

Been through this? Let me know.