How to find app testers for free (Android and iOS)

Short answer: the best free testers are people who already have the problem your app solves. Start with a small circle you can reach directly (friends, coworkers, your newsletter or social followers), then go to communities of your future users and of other developers: subreddits, Discord servers, indie dev forums and sites like TrueLaunch where people try new apps and leave honest, structured feedback. Make joining take one tap (a Google Play opt-in link or a TestFlight public link), give testers a short list of things to try, and reply to everyone who helps.

Why do I need app testers at all?

You can't see your own app with fresh eyes. Testers find the crashes on devices you don't own, the button nobody notices and the step where people give up. On Android there is also a hard requirement: new personal Google Play developer accounts need a closed test with real testers before they can publish to production (more on that below).

Where can I find app testers for free?

1. People you already know

Friends, family and coworkers are the fastest start, and they're fine for catching crashes and setup problems. Their limits: they're often not your audience, they tend to be kind rather than honest, and on Android many of them may use iPhones. Use them for the first round, not the only one.

2. Your own audience

If you have a newsletter, a waitlist, a social account or an earlier app, ask there. These people chose to follow your work, so they're more likely to open the build and tell you what they think. A short "I'm looking for 15 Android testers for two weeks" post with the opt-in link works better than a general announcement.

3. Communities of your future users

Look for places where people talk about the problem your app solves: a subreddit for runners, a Discord for budget planners, a forum for a game genre. Read the rules first, since many only allow "looking for testers" posts in a weekly thread. Explain what the app does, what kind of feedback you need and how long testing lasts. Our guide on promoting your app on Reddit without getting banned covers how to post there.

4. Communities of developers

Subreddits and Discord servers for indie developers, Android and iOS developers and game developers often have threads where makers test each other's builds. Other developers are good at spotting bugs and describing them clearly. Be careful with groups that trade store ratings or reviews in return for testing: that breaks Google Play and App Store policies and can get your app removed. Ask for testing and feedback only.

5. TrueLaunch

List your app on TrueLaunch for free. People browse new apps and games, try them and leave structured feedback: what worked, what to improve and any bugs they hit. Reviews stay on TrueLaunch and are never traded for store ratings, so you get honest notes without risking your store account.

6. Beta testing platforms

Some platforms connect developers with testers or manage feedback for you. Several have free tiers. See beta testing platforms for indie developers for a comparison.

How do I get testers for Google Play?

Google Play has three testing tracks: internal, closed and open. For most indie apps you'll use closed testing, where you add testers by email list or Google Group and share an opt-in link.

If your personal developer account was created after November 13, 2023, Google requires a closed test with at least 12 testers who stay opted in for 14 days in a row before you can apply for production access. Organization accounts are not covered by this rule. Recruit 15 to 20 people so a few dropping out doesn't restart your count, and ask them to actually use the app, because the production application asks what you learned from the test.

Full details are in how to get 12 testers for Google Play closed testing, and the differences between the tracks are in internal, closed and open testing explained.

How do I add TestFlight testers on iOS?

TestFlight has two kinds of testers:

• Internal testers: up to 100 members of your App Store Connect team. They can install builds as soon as processing finishes.
• External testers: Apple says you can invite up to 10,000 people. You can add them by email or share a public link, so anyone with the link can join without you collecting addresses. The first build you send to external testers has to pass Beta App Review, and you need to fill in a beta description and review information first.

Builds expire 90 days after upload. Step-by-step setup is in how to use TestFlight for beta testing.

How do I keep testers active?

Finding testers is half the work. Keeping them is the other half:

• Make joining easy. One link, clear install steps, and a note about which Google account or Apple ID to use.
• Give a short task list. "Sign up, add your first habit, set a reminder, tell us what confused you" gets far better feedback than "let me know what you think". A beta test plan helps.
• Ask specific questions. Where did you get stuck? What did you expect to happen? What would you remove?
• Ship updates and say so. A short "fixed the crash you reported, thanks Ravi" message keeps people opening new builds.
• Thank people publicly. Credit testers in release notes or an "early supporters" list if they agree.
• Don't pay for reviews or reward ratings. Paying or rewarding people for store ratings breaks store rules. Testing and feedback are what you're asking for.

How many testers do I need?

For finding crashes and confusing screens, a handful of engaged testers goes a long way. For Google Play's production requirement you need at least 12 opted in for 14 days. For games, aim for players who already love the genre: our guide on finding playtesters for your indie game has more ideas.

Next steps

Write a two-line "looking for testers" post with your opt-in or TestFlight link, share it with your own circle today, and post it in one or two communities whose rules allow it. Then list your app on TrueLaunch for free to get honest, structured feedback from people around the world.