1
2 Comments

How do you get your first 12 beta testers when you have no audience?

Genuine question, but also sharing what I'm doing right now with a real app.

I built Billd — an Android income tracker for freelancers. You set your hourly rate, log hours daily, see earned vs missed income. No backend, no accounts. Built it in Flutter with zero prior Flutter experience.

It's in Google Play closed testing. The rule: I need 12 testers who stay active for 14 days before Google unlocks production publishing. I have 1 right now.

Here's what I've tried so far:

  • Posted my build story on IH main feed (1 comment, 0 form submissions yet)
  • Joined 6 IH groups and cross-posting (this post)
  • Google Form for Gmail collection: https://forms.gle/5KeUW3XF5HYeHxq7A
  • Reddit is a dead end for me — low karma account, posts get shadow-removed

What actually worked for you to get those first 10-15 beta testers? Especially with no existing audience.

If you're a freelancer on Android, I'd genuinely love you as a tester — fills out in 20 seconds.

on March 29, 2026
  1. 1

    The no-audience angle is painfully familiar. What helped me think about Kinetic Override was not asking “who wants to test an app?”, but finding people already doing the exact repetitive Android workflow: taps, swipes, timing loops, no-root constraints. The narrower the pain, the easier it is to tell whether a tester is actually qualified.

  2. 1

    For Android beta testing, I would bias toward people who already feel the exact pain, not generic swaps. With Kinetic Override that means users who search for no-root auto clicker, macro recorder, or record taps on Android — they notice onboarding and permission issues faster.