How to Get Beta Testers for Your App (iOS, Android, Web)

How do you get beta testers for your app?

To get beta testers for your app, distribute the beta through the official channels, TestFlight for iOS and other Apple platforms and the testing tracks in Google Play Console for Android, and recruit testers from people who match your target users: your own network and waitlist, niche communities, beta listing sites, and, when you need fast structured feedback, paid tasks that ask people to use a feature and report what happened. The best testers are not the most numerous ones, but the ones who actually use the app and tell you where it breaks.

Decide what kind of beta you are running

“Beta testers” covers three different jobs, and each needs different people:

• Technical testing: crashes, device and OS problems, broken flows. You need many different devices and testers who report bugs clearly.
• Usability testing: where people get stuck and what confuses them. Fresh eyes from strangers matter more than numbers.
• Market validation: whether people want the app and come back. You need testers who match your target users and use the app over days or weeks.

Write down which of the three you need most. It decides where you recruit and what you ask testers to do.

Beta testing on iOS with TestFlight

TestFlight is Apple’s official beta tool, managed in App Store Connect. According to Apple’s documentation:

• Internal testers: up to 100 members of your team who have access in App Store Connect.
• External testers: up to 10,000 people, invited by email or through a public link you can share anywhere.
• Review: the first build you add to an external testing group is sent to App Review; later builds may not need a full review.
• Build lifetime: each build is available for testing for up to 90 days.

The public link is the easiest way to recruit strangers, because nobody has to give you an email address. You can set criteria on a public link, which limits who can join. Testers can send feedback, including screenshots, through the TestFlight app.

Beta testing on Android with Google Play

Google Play Console has three testing tracks:

In closed and open tests, testers can send you private feedback through Google Play, and they cannot leave public reviews on test versions.

The closed testing requirement for new personal accounts

Google’s Play Console Help describes a specific rule for personal developer accounts created after November 13, 2023: before you can apply for production access, your app must have run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Open testing becomes available only after you gain production access, and the application asks how engaged your testers were and what you changed because of their feedback. Google Play’s 12-tester rule explained covers the setup, the application questions, and a 14-day plan for keeping testers engaged.

For your beta plan, three things matter:

• Recruit more than 12 people who will actually use the app for two weeks, because some will opt out or never open it.
• Start early. The 14 days and Google’s review of your application both come before your public launch.
• Keep notes of feedback and the changes you made, because the application asks for exactly that.

Do not try to fill the requirement with people who opt in and never test. It leaves you with nothing to report on engagement or feedback, which is what Google asks about. We do not recommend buying tester slots, and Sharklio campaigns are not a way to fill a closed test. Check the current Play Console Help page before you plan, because Google updates the requirement from time to time.

Web apps and desktop software

A web app needs no store approval: a sign-up page with an invite code or a waitlist is your beta channel. Use a separate environment or a feature flag for beta features, and add an in-app feedback button so testers can report issues in context. Desktop software can be shared as a download from your site, ideally with crash reporting turned on and a clear note that it is a beta.

Where to find beta testers

1. Your waitlist and existing users. People who signed up early are the most motivated testers you will find. Invite them personally and explain what you need.
2. Your personal and professional network. Good for the first few testers and for filling a closed test with people who will actually use the app. Ask them to bring one friend who fits the target group.
3. Niche communities. Forums, subreddits, and Discord or Slack groups around the problem your app solves. Read the rules, contribute first, and post a clear invitation where it is allowed.
4. Beta listing sites and maker communities. Sites that list upcoming products and communities of indie makers attract early adopters who enjoy trying new things.
5. Social posts and build-in-public updates. Sharing progress openly builds a small audience that is often happy to test.
6. Paid feedback tasks. When you need structured feedback from strangers quickly, see the next section.

Building a game? How to find playtesters covers game-specific sources such as Steam Playtest, itch.io, and genre communities.

Paid feedback tasks: install, use a feature, report back

If the app is already available to the public, for example through a TestFlight public link, an open testing track after production access, a live app with a new feature, or a web beta, you can pay people to try a specific part of it and send structured feedback. On per-result platforms such as offerwalls, users of other sites and apps choose the task, are rewarded by the publisher, and you pay per completed result.

A few rules make these tasks useful and fair:

• Ask one specific question about one feature. “Any feedback?” gets one-word answers.
• Use Screenshot and Text proof, so you see where the tester got to and what they thought.
• Target the devices and OS your app supports.
• Never reject negative feedback. Reject only when the proof is missing or clearly fails the requirement. Critical answers are the most valuable ones.
• Never mention ratings or reviews in the task, and do not trigger a rating prompt as part of it.

Keep the limits in mind too. Rewarded testers are strangers who came for the reward, so they are good for first impressions and usability problems, and weaker for judging long-term demand. Incentivized traffic explained covers when rewarded users fit. On Sharklio, completion details may be used only to review and measure the campaign, so recruit people you want to interview later through your own channels.

For the proof wording, Proof requirements by task type has copy-ready examples for app tasks.

What you must never pay for

Paying for store ratings or reviews, or rewarding testers for them, breaks Google Play and App Store policies, whatever the wording and whether the review is positive or not. It can lead to rejected updates, removal of the app, or action against the developer account. Can you pay for app reviews? quotes the store rules. Ask for ratings only through the official in-app review prompts, without a reward, once the app is live.

How to turn testers into useful feedback

• Give a short brief with three to five things to try, not “play around with it”.
• Make reporting easy: an in-app feedback button, the store’s feedback channel, or a short form with the device and OS filled in.
• Turn on crash reporting and analytics so you see problems testers do not report.
• Reply to every report and tell testers what you fixed. People who see their feedback used keep testing.
• Ship small updates often, and ask testers to retry the part that was fixed.

When the beta ends, thank your testers and, if you like, give them something within the app, such as an extended free plan, without tying it to a rating. When you are ready for launch, How to get app installs covers the next stage.

Frequently asked questions