As an indie developer, I thought the hardest part of creating my first Android app was the actual coding. Boy, was I wrong.
After months of development, I finally had my app ready. I created my Google Play Console account, uploaded my APK, filled out all the store listing details, and was practically bouncing in my chair, ready to hit "publish." That's when I discovered Google's 12-tester requirement.
The Reality Check
Google Play now requires new developer accounts to have their apps tested by at least 12 testers for 14 consecutive days before you can even apply for production access. At first, I thought "12 people? That's nothing!" But reality hit hard when I realized most of my friends and family use iPhones.
Publish a closed testing release
Have at least 12 testers opted-in to your closed test
Run your closed test with at least 12 testers, for at least 14 days
I spent hours reading developer forums, and what I found was terrifying. Even developers who managed to find 12 testers were getting rejected for production access. Some had been waiting months. The anxiety was real, what if all my work was for nothing?
Setting Up the Testing
First things first, I needed to create a proper testing setup. In the Google Play Console, I navigated to "Testing > Closed testing" and created a new track. The interface is pretty straightforward, but there's one crucial decision: how to manage your testers.
Google gives you two options:
- Email lists (manually adding individual emails)
- Google Groups (creating a group that testers can join)
I initially considered the email list approach, but quickly realized it would be a nightmare to manage. Every time I wanted to add a tester, I'd need their exact Gmail address. Plus, users don't really like sharing their emails with random developers.
So I created a Google Group instead. I named it something simple but clear, set it to "Anyone can join".
Finding Testers
Trying Friends and Family
With my Google Group ready, I started calling up my colleagues, friends and family asking them to join. I got maybe 4-5 people to install it, and honestly, I could tell they were just being polite. Half of them uninstalled within a few days.
Exploring Reddit Communities
Desperate times called for desperate measures. I turned to Reddit and found r/androiddev. I posted explaining my situation, asking if anyone could help test my app. The response was mixed – some helpful suggestions, a few installs, but still nowhere near 12 consistent testers. Within few hours also my post got removed by mods(typical reddit mods...)
Testers Community App
While desperately Googling solutions, I stumbled across a YouTube video where another indie dev shared their experience with the same problem. They mentioned using a app called the "Testers Community", essentially a platform where you test other people's apps to earn credits, then use those credits to get testers for your own app.
I was skeptical at first (another app to download?), but desperation made me try it. The concept was simple: test 3 apps from other developers, get enough credits to post your own app for testing.
App Link: https://play.google.com/store/apps/details?id=com.testerscommunity
Within 2 days, I had 14 testers. I couldn't believe it actually worked.I kept adding my app on this community for 14 days.
Other Communities
Through the app, I also discovered there's an active subreddit called r/TestersCommunity. Unlike other places I'd tried, this community was specifically built around mutual testing help. People were actively posting their apps, giving feedback, and genuinely trying to help each other navigate Google's requirements.
The best part? It was completely free.
I kept posting updates, responding to feedback, and testing other developers' apps in return. By the end of my 14-day testing period, I had close to 60 testers total which is way more than the minimum requirement.
What I Learned
During this whole process, I spent hours reading blogs and developer experiences with Google's testing requirements. Based on those insights and my own journey, here are the key tips I'd recommend to any developer facing this challenge:
Aim for 20-30 testers, not just 12. This was the most important lesson I learned from other developers' experiences. Some users will uninstall early, others might not meet Google's mysterious "activity requirements." Having a buffer of extra testers significantly increases your chances of success.
Push frequent updates during your 14-day period. I ended up releasing 6 small updates during my testing window. While I can't prove it definitively, I'm convinced this demonstrated to Google that my app was actively maintained and not abandoned. Other successful developers I read about followed similar patterns.
Take the production access form seriously. After your 14 days are up, Google asks you to fill out a detailed application form. This is where many developers get rejected, even after successfully completing the testing period. Take your time with this - write clear, detailed answers about your app's purpose, target audience, and compliance with Google's policies.
For more detailed guidance on avoiding rejections during the production access application, I found this comprehensive guide extremely helpful.
The Waiting Game
After completing my 14-day test, I submitted my production access application. The form asked detailed questions about my app's purpose, target audience, and how it complies with Google's policies. I spent hours crafting detailed responses, knowing that many developers get rejected at this stage.
Two days later, I got approved. The relief was incredible.
Final Thoughts
Google's 12-tester policy initially felt like an impossible hurdle, but it taught me the value of community in indie development. The developers I met while finding testers have become ongoing connections – we still help each other with testing new features and updates.
If you're stuck at the same roadblock, don't panic. The testers are out there, and the communities exist to help. You just need to know where to look and be willing to help others in return.
The indie dev journey is tough enough without facing these hurdles alone. Sometimes the best solution is simply finding your tribe.
Have you dealt with Google's testing requirements? What worked for you? I'd love to hear other developers' experiences in the comments.
Resources That Helped Me
r/AndroidDev - Android developers subreddit
Testers Community App - Free mutual testing platform
r/TestersCommunity - Active Reddit community for app testing
Google Group - You can create a google group here
Youtube Video - Video explaining about the community
Top comments (0)