When I finished my app SnapReturn this fall, I hit the same wall a lot of indie Android developers hit: Google wouldn't let me publish to production until I ran a closed test with at least 12 testers for 14 days. I'm an Android developer by day, so I figured this part would be easy. It wasn't.
I got one friend and three family members. My Reddit posts got a few replies, and some of those people disappeared after a day or two. What finally got me through was a group of developers testing each other's apps. Here's everything I learned along the way.
The rule, in 30 seconds
If your personal Play Console account was created after November 13, 2023, you need to run a closed test before you can publish to production. It needs at least 12 testers who stay opted in continuously for at least 14 days. Then you answer a set of questions about your test and wait for Google to review your application.
- The 14 days must be consecutive, and testers who leave early don't count.
- A tester who opts out and back in starts their count again.
- Organization accounts don't have this rule.
Google's rules can change, so check Google's help page for the latest.
Why "12 opted in" isn't enough
The number is the easy part to understand. The part that trips people up is engagement. When you apply for production, Google asks how engaged your testers were, what feedback they gave, and what you changed because of it. Developers regularly report being asked to keep testing even after reaching 12, because their testers barely opened the app.
So the real goal isn't 12 names on a list. It's 12+ people who actually use your app, often enough that your answers to Google are true and specific.
Where to find testers
Friends and family
Good: Reliable and honest
Watch out: Few people, and some will have iPhones. Rarely enough on its own.
Reddit swap posts (r/AndroidClosedTesting, r/TestersCommunity)
Good: Free, and full of people in the same spot
Watch out: People drop off quietly. Keep a list of whose app you're testing, and keep your end of every swap.
Tester-swap communities and apps
Good: A built-in group of developers who need the same thing
Watch out: Check how they confirm people actually test, not just opt in.
Paid tester services
Good: Fast
Watch out: Be careful with anything that promises approval. Google decides that, and testers who never really use your app don't help your application.
Your own users (email list, social, an existing app)
Good: Real future users, with real feedback
Watch out: Only works if you already have an audience.
Recruit 15–20, not 12. Someone always drops out, and a spare tester only helps if they opted in from the start.
Set up your test so nobody gets stuck
- Use a Google Group for testers. Anyone can join it, and you add the group to your closed track once, instead of collecting everyone's email.
- Make the test available in all countries. If it's limited to your country, testers elsewhere can't install it, and they won't always tell you.
- Share the "Join on the web" link from your closed track, and remind people to use the same Google account for the group and the opt-in.
- Publish the release and wait for Google's review of the closed track before you send the link. An unreviewed track shows testers an error.
Keep testers engaged for 14 days
- Give a small task each day. "Open the app" gets ignored. "Add a recipe from a website" gets done, and it gets the part you care about tested.
- Keep tasks short. A couple of minutes is the sweet spot. Your testers are doing you a favor.
- Ask for one sentence of feedback: what worked, and what got in the way. Short notes add up to real evidence.
- Ship at least one update during the test, and tell testers what you fixed. It shows Google the test changed your app.
- Check Play Console's tester count every few days. It's the number Google uses.
Write down what happens as you go
When you apply for production, Google asks about three things:
- Your closed test: how you recruited testers, whether they used all your features, and what feedback they gave
- Your app: who it's for, its value, and how many installs you expect in the first year
- Your readiness: what you changed after testing, and how you decided the app was ready
It's much easier to answer honestly if you kept notes: which features got tested, the problems testers found, and what you fixed. Specific, true answers hold up. Vague or exaggerated ones don't.
The short version
- Recruit 15–20 testers, not 12.
- Use a Google Group and make the test available in all countries.
- Give testers a short task every day.
- Fix what they find, ship an update, and keep notes.
- Answer Google's questions with what really happened.
After going through this myself, I built Fourteen, where groups of 16 Android developers test each other's apps daily for 14 days, with short tasks and an optional SDK that confirms real use. It also drafts your answers to Google's questions from your test data. The first cohort begins Saturday, November 14, 2026. Whatever route you take, I hope this saves you some of the time it cost me.
Fourteen is an independent project and isn't affiliated with or endorsed by Google. Google's rules can change, so check Google's help page for the latest.
Originally published at getfourteen.app.
