TestSwap
All posts

How to find beta testers for your app (for free)

· 7 min read

If you're wondering how to find beta testers for your app without paying for them, here's the short version: there's no single best place. There are several free options, and each one is good at one thing and bad at another. This guide goes through them honestly, including the one I built.

Before you start, decide what you need. "Some people to try it and tell me what's confusing" is a different job from "12 people installed on Android for two weeks so Google lets me publish." The right option depends on which one you mean.

First, get your ask right

Whatever channel you use, the quality of the feedback depends mostly on what you ask for. "Please test my app" gets "looks cool." A single concrete task gets something you can act on. I wrote up how to do that in how to write a test task. Read it before you post anywhere.

1. People you know (and their friends)

Good for: a first sanity check, catching crashes, and getting real-world device coverage quickly.

The catch: people who like you are polite. Ask them to do one specific thing and watch them do it, or at least ask where they got stuck, not whether they liked it. Friends of friends are better than friends, because they owe you less.

2. Reddit communities

There are subreddits built for exactly this. Three I'd look at are r/TestMyApp, r/AlphaAndBetausers and r/betatests. Communities aimed at your app's topic can work even better, for example a running subreddit for a running app.

Good for: reaching strangers who like trying new things, at no cost.

The catch: many posters are other developers who want testers too, so replies can be thin and you may be expected to test their app in return. Every subreddit has its own self-promotion rules, so read them first or your post will be removed. Say what the app does, what you want tested and how long it takes. Don't paste a bare link.

3. Indie Hackers and other maker communities

Indie Hackers has an active forum where founders talk about what they're building. Posting an honest "here's what I made and what I'm unsure about" thread, and replying to other people's threads, tends to work better than dropping a link.

Good for: thoughtful feedback from people who build things themselves, and for finding your first few fans.

The catch: it's a conversation, not a service. You'll get out roughly what you put in, and it takes time.

4. Directories like BetaList

BetaList lists pre-launch products for people who like to discover new ones. It suits web products and startups more than a small utility app.

Good for: getting early sign-ups and a bit of visibility before launch.

The catch: free submissions can involve a wait, and visitors tend to sign up rather than test and write back. Check their current terms before you count on it. It's a discovery channel more than a feedback channel.

5. Your own audience on X, LinkedIn or a newsletter

If you have followers, even 200 of them, a clear post saying "I need five people to try this for ten minutes" often works better than anything on this list. Mention one thing you're unsure about, and say what you'll do with the answers.

Good for: feedback from people who already know your work.

The catch: if you're starting from zero followers, there's nobody to ask yet.

6. TestFlight (iOS)

Apple's TestFlight lets you invite outside testers by email or with a public link. According to Apple's App Store Connect help, you can have up to 10,000 external testers, and the first build you give external testers has to pass a beta app review first.

Good for: distributing an iOS build to anyone, with a single link you can post anywhere above.

The catch: TestFlight is a delivery tool. It doesn't find testers for you. You still need to bring the people, and you need an Apple developer account to use it.

7. Google Play closed testing (Android)

This one is different, because it can be mandatory. Per Google's Play Console help, new personal developer accounts must run a closed test with at least 12 testers opted in for at least 14 days before they can apply for production access. Check that page for the rule that applies to your account, because Google has changed this requirement before.

Good for: meeting that requirement, and getting early Android feedback on a real install.

The catch: the testers must actually opt in to your closed test and keep it installed, which is a lot to ask of strangers. Plan for some to drop out, and recruit more than 12. There are also tester-exchange apps built specifically for this requirement. If you use one, read what it asks of you and what it gives you before you hand over your app.

8. A tester swap like TestSwap

I built TestSwap because I wanted a fair trade. The pitch is "give a test, get a test." You review other developers' apps, earn a credit for each review, and spend credits so others review yours. You sign in with X, and new accounts start with 3 credits. It's free and there are no paid tiers. Web, iOS and Android apps are all welcome, and each app has a test task that tells reviewers what to do. You can read the full reasoning in why I built it.

Good for: a handful of thoughtful reviews from people who build apps themselves and know what useful feedback looks like. Each review has a public part about the UX, a public part on what to improve, and optional private bug notes only you can see.

The catch, plainly:

  • It does not satisfy Google Play's closed-testing requirement. Those testers need to opt in to your Play closed test and stay opted in for the required days. TestSwap reviewers don't do that.
  • It's a handful of reviews, not mass QA. Don't expect hundreds of devices or a full regression pass.
  • It's brand new. It launched in October 2026, so the feed is small while it grows. I have no numbers to show you yet.
  • You have to give to get. You earn credits by reviewing, and your apps pause when your balance hits 0.
  • Reviews are rated. You can rate each review once with a 👍 or 👎, and a 👎 takes back the reviewer's credit. That discourages lazy reviews, but it also means you should be sure before you click.

Tips that work on every channel

  • Ask for one thing. A task that takes ten minutes gets done.
  • Give a starting link. A URL, a TestFlight link or a Play link. No hunting.
  • Say what you're unsure about. Testers will look hardest where you point.
  • Offer a throwaway demo account. Never share a password you use anywhere else.
  • Reply to everyone. A thank-you and a note about what you changed gets you a second review later.
  • Send a stable build. Feedback on a half-broken build mostly tells you what you already know.

Which one when

  • "I need a quick sanity check this week": people you know, plus a post to your own followers.
  • "I want feedback from strangers on a web app": Reddit tester communities and Indie Hackers.
  • "I want builders to look at the UX in detail": a tester swap like TestSwap, with a sharp test task.
  • "I'm launching soon and want sign-ups": a directory like BetaList.
  • "I need iOS testers outside my team": TestFlight with a public link, shared on any of the channels above.
  • "Google Play won't let me go to production": a proper closed test with at least 12 opted-in testers for at least 14 days, as Google requires. Check Google's page for the current rule.

Most people end up combining two or three. Start with the one that matches what you need this week, and write a good test task before you post anywhere.