How to find beta testers for your Flutter app (when you don't have a network)
Six channels that actually work for finding beta testers when you're an indie developer with zero followers. Ranked by effort and signal quality.
You shipped your Flutter app to TestFlight or Play Internal Track. You opened the tester invite link and… nothing. You have 4 followers on Twitter. Your wife already saw the app. Your cousin gave a thumbs-up emoji to your launch post a week ago and still hasn’t installed it.
This is the indie-developer beta-tester problem. It has solutions, but they’re not the ones most blog posts recommend. Here’s the actual ranked list of channels that work, sorted by effort vs. signal quality.
Why this is hard in the first place
Most “find beta testers” advice was written for product teams at funded startups with a marketing budget, an existing email list, and a community manager. None of that applies to a solo dev shipping their first Flutter app.
The asymmetry is real: a beta tester carries the risk (your app might crash on their device, eat their data, drain their battery), and you get the value (their feedback). Without a pre-existing relationship, you need to offset that asymmetry with one of three things:
- Community currency — they already follow you or trust your work.
- Incentive — they get paid, or get the app, or get a status badge.
- A marketplace — someone else aggregated testers already, and you rent access.
Almost every channel below uses one of those three levers. Pick based on which lever you have.
1. Your own audience (effort: low if you have one)
Effort: 30 minutes Signal quality: Very high Cost: Free Limit: You probably have ≤10 people here
If you have any audience at all — Twitter followers, mailing list, Discord members, Indie Hackers profile — start here. People who follow your work already cleared the trust threshold and will give you honest feedback.
The trick is to ask SPECIFICALLY: “I’m beta-testing a Flutter app for tracking grocery receipts. I need 5 people to scan 3 receipts each over the next 2 weeks. iOS or Android, both fine. Reply if you’re in.” Vague asks (“anyone want to test my app?”) get vague responses.
If you have 0 audience: skip this. Don’t spend 6 months building one before you ship — that’s procrastination wearing a productivity costume. Use channels 2-6.
2. r/FlutterDev and other developer communities (effort: medium)
Effort: 1–3 hours per post Signal quality: Medium (testers are also developers, biased toward technical bugs) Cost: Free Yield: 3–8 testers per well-targeted post
Subreddits and Discord channels that work:
- r/FlutterDev — strict on spam; post with a real screenshot and a “looking for feedback” framing, not a launch pitch
- r/SideProject — friendlier to early projects
- r/androidapps and r/iOSBeta — explicitly for beta testing
- Flutter Discord —
#showcasechannel - Indie Hackers — post in the appropriate group
The catch: developer testers find developer bugs. They’ll flag your input validation but they probably won’t notice that the onboarding flow is confusing for a non-technical user. Pair this channel with channel 4 or 6 for real-user signal.
3. BetaList, Product Hunt Ship, AppCoda Tester (effort: medium-high)
Effort: 2–4 hours for the listing + ongoing replies Signal quality: Medium-high Cost: Free or low ($30–$50 for boosted listings) Yield: 20–80 signups per listing, of which 5–15 actually install
Curated directories that pair pre-launch apps with people who specifically signed up to test pre-launch apps. The selection is decent because the audience self-identified as wanting to try new things.
The trap: a “signup” on BetaList isn’t the same as an installed-app-with-feedback. Roughly 1 in 5 signups converts to actual testing. Plan for that drop-off.
4. Direct outreach to people who’d actually want your app (effort: high, signal: highest)
Effort: 4–8 hours, depends on your niche Signal quality: Highest — these are your real users Cost: Free Yield: 5–20 testers if your targeting is good
Skip the developer communities. Find the people who would actually USE the app once it ships, and ask THEM. If you built a receipt-tracker, that’s people in r/personalfinance, r/Frugal, r/EatCheapAndHealthy. If you built a Flutter app for chess training, it’s r/chess.
The script: “Hi, I’m building [X] for [the problem they have]. I’ve shipped a beta to TestFlight / Play Internal. Would you be willing to try it for a week and tell me what’s broken? I’m not selling anything, I just need real-user feedback.”
This converts at 5–15% per cold-DM. With 50 DMs you’ll get 5–8 testers. Slower than channel 3 but their feedback is gold because they actually want what you’re building.
5. “Looking for beta testers” tweets (effort: low, signal: lottery)
Effort: 20 minutes Signal quality: Low-medium, depends on luck Cost: Free Yield: 0–20 testers, highly variable
There’s a small ecosystem of accounts that retweet “looking for beta testers” posts: @BetaListing, @AppGoodies, various #buildinpublic regulars. Tag them and use #buildinpublic, #100DaysOfCode, #FlutterDev, #indiedev.
This works occasionally. It’s not predictable. Treat it as a small bet alongside other channels, not a primary strategy.
6. Crowd-testing platforms (effort: lowest, signal: highest within scope)
Effort: 30 minutes setup + 5 minutes per test campaign Signal quality: High (structured bug reports with repro steps + device context) Cost: €30–€300 per campaign depending on tester count Yield: Exactly what you ordered (8–20 testers, 24–48 hour turnaround)
The trade-off is money for time. Instead of spending 8 hours posting in communities and waiting weeks, you spend €100–€200 and have structured findings in 48 hours.
Three platforms that work for indie devs:
- TesterPayKit — EU-hosted, DSGVO-compliant, designed for AI-built and Flutter apps. €0 to start, pay-per-tester.
- TestFi — $1.99–$3.99 per tester, no SDK required, 12+ countries.
- Beta Family — older platform, 965K+ tester pool, more enterprise-flavored.
Use this when: you have a deadline, you’ve already tested with friends and found nothing, or you need device-specific coverage (a specific Android model, an older iOS version) that your existing channels can’t deliver.
Don’t use this when: you have zero clue what your app should do yet — that’s the user-research phase, not the bug-finding phase. See our pillar post on what is crowd testing vs. user testing.
The honest ranked list
For an indie dev shipping a Flutter app with no existing audience:
| Rank | Channel | When to use |
|---|---|---|
| 1 | Direct outreach to your actual user persona | If you have time + know who your user is |
| 2 | Crowd-testing platform | If you have a deadline or want device coverage |
| 3 | r/FlutterDev / Discord | Free + gets you technical eyes on the build |
| 4 | BetaList / Product Hunt Ship | If you’re 2-3 weeks pre-launch and want a pipeline |
| 5 | Your own audience | If you have one — otherwise skip |
| 6 | Lottery tweets | Background noise, free, occasionally lucky |
Stack them, don’t pick one
The single biggest mistake indie devs make: picking one channel and waiting. Run channel 2 (community posts) AND channel 4 (direct outreach) AND channel 6 (one paid crowd campaign) IN PARALLEL. The compounding signal is what matters — not which one is “best”.
A realistic mix for a 3-week beta: 1 community post per week (channel 2), 10 cold-DMs per day for the first week (channel 4), one €100 crowd-testing campaign in week 2 (channel 6). Total cost: ~€100 + ~15 hours of your time. Total testers: 15–25. Total feedback quality: high because each channel contributes a different signal type.
When to stop and ship
If you’ve collected 15+ actionable bug reports and you’re no longer hearing new things, you’re done with beta. Polish the top 3-5 fixes and ship. Beta forever is procrastination; beta-then-ship is iteration.
This post is part of TesterPayKit’s crowd-testing series. The pillar: What is crowd testing? — start there if you’re new to the topic.