Hello! Today I want to compare the different ways to find testers for Google's closed testing requirement, along with the pros and cons of each.
Background
In 2023, Google updated its app publishing policy, making it significantly harder for indie developers to get started. Since affected developers need to find testers every time they release an app, it's not practical to figure it out from scratch each time.
Methods Compared
A quick note: I haven't personally used every method on this list, so some of this includes my own estimates. I'm also writing for new indie developers, so methods like using internal company testers aren't included.
Here are the options I can think of:
- Use your personal network
- Use social media
- Attend developer meetups
- Pay for a tester service
- Use a dedicated closed testing app
1. Use Your Personal Network
This means explaining the situation to family and friends and asking them to participate as testers.
Pros
- Guaranteed testers
- Free
Cons
- Limited by how many people you know (especially if you're an introvert)
- Can feel embarrassing
- Hard to ask repeatedly (especially if you're developing multiple apps)
- Explaining how to test can be tedious (especially if they're not tech-savvy)
This is the easiest and most reliable method — but not many people can reach 20 testers through personal connections alone.
2. Use Social Media
This typically means platforms like Discord and Reddit, where you exchange testing — you test their app, they test yours.
Pros
- Access to a large pool of developers
- Free
- Less explanation needed about your background
Cons
- Takes time to find the right people
- English is essentially required (hard to find enough testers domestically)
- You'll end up installing apps you have no interest in
- Some people make false reports about completing tests
Free and ultimately effective, but time-consuming.
3. Attend Meetups
Going to events and asking other attendees to test your app.
Pros
- Great for learning from other developers
- Can secure testers reliably
- Free (depending on the event)
Cons
- Takes time
- No guarantee of reaching 20 testers
I haven't tried this myself, but meetups are primarily about networking — getting testers should probably be treated as a bonus, not the main goal.
4. Pay for a Tester Service
Signing up for a service that provides dedicated devices for closed testing. A quick search will turn up various options.
Pros
- Fast
- Low effort
Cons
- Costs money
- Quality and trustworthiness can be hard to verify
The quickest option. May be worth it if you have budget or expect your app to recoup the cost quickly.
5. Use a Dedicated Closed Testing App
Using a dedicated app to test other developers' apps in exchange for having your own app tested.
Pros
- Low effort
- Free
- You can choose apps you're actually interested in (compared to social media)
- No English required (no need to negotiate with other developers directly)
Cons
- May take time depending on tester availability
No major downsides here. Similar to the social media approach, but with the friction removed — no need to communicate directly with other developers in English.
Overall Comparison
You don't have to pick just one method — using multiple in parallel based on your situation is the smart move. Meetups are a bit of a special case. If budget isn't a concern and you're okay with the trust risk, a paid service is the fastest path. Otherwise, a combination of personal network, social media, and a dedicated app should cover you.