This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
BetaLobby
Meet Google Play’s 12-tester rule free, no paid testers
Stop chasing test-for-test swaps in forums. BetaLobby matches indie Android developers into 16-person teams (Team mode) or 1:1 matches (Auto Pair), so everyone gets 12+ testers for Google Play's 14-day closed test. - One shared Google Group: no per-app groups or opt-in link swapping - Installs and daily check-ins verified on the device, no screenshots - TRUST score keeps testers showing up for all 14 days, no ghosting Free, no paid plans.
If you've launched an Android app on a personal Google Play developer account recently, you know the pain: before you can apply for access to production, you must run a closed test with at least 12 testers opted-in for at least 14 days.
Finding testers in forums is exhausting. You end up joining a dozen separate Google Groups, hitting "Item not found" on Google Play, chasing screenshots in DMs, and getting ghosted by testers who install your app once and never open it again.
I built BetaLobby to take the friction out of the whole closed testing workflow, and just used it to pass closed testing and release BetaLobby itself to production on Google Play:
• One Google Group & pre-checked apps: join a single shared Google Group once. Every submitted app is checked for the group setup and region availability first, so no more joining 15 different groups or hitting "Item not found."
• Team mode & Auto Pair: join a 16-developer team (15 testers, a 3-tester buffer above the 12-tester requirement) or match 1:1 at your own pace.
• On-device install verification: zero screenshots. BetaLobby confirms installs directly on the device.
• Daily check-ins & TRUST: installing once isn't enough. BetaLobby tracks daily check-ins (actually opening the apps across the 14 days) with push reminders, backed by a 100-point TRUST score that penalizes freeloaders and early dropouts.
BetaLobby is completely free, no paid plans. Built by an indie dev for indie devs.
What was the hardest part of your own closed test? I'd love to hear it.
No comment highlights available yet. Please check back later!
About BetaLobby on Product Hunt
“Meet Google Play’s 12-tester rule free, no paid testers”
BetaLobby was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #179 on the daily leaderboard. Stop chasing test-for-test swaps in forums. BetaLobby matches indie Android developers into 16-person teams (Team mode) or 1:1 matches (Auto Pair), so everyone gets 12+ testers for Google Play's 14-day closed test. - One shared Google Group: no per-app groups or opt-in link swapping - Installs and daily check-ins verified on the device, no screenshots - TRUST score keeps testers showing up for all 14 days, no ghosting Free, no paid plans.
BetaLobby was featured in Android (57.7k followers), Developer Tools (521.6k followers) and Maker Tools (2.9k followers) on Product Hunt. Together, these topics include over 142.4k products, making this a competitive space to launch in.
Who hunted BetaLobby?
BetaLobby was hunted by Jay. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how BetaLobby stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Jay
Hey Product Hunt! 👋
If you've launched an Android app on a personal Google Play developer account recently, you know the pain: before you can apply for access to production, you must run a closed test with at least 12 testers opted-in for at least 14 days.
Finding testers in forums is exhausting. You end up joining a dozen separate Google Groups, hitting "Item not found" on Google Play, chasing screenshots in DMs, and getting ghosted by testers who install your app once and never open it again.
I built BetaLobby to take the friction out of the whole closed testing workflow, and just used it to pass closed testing and release BetaLobby itself to production on Google Play:
• One Google Group & pre-checked apps: join a single shared Google Group once. Every submitted app is checked for the group setup and region availability first, so no more joining 15 different groups or hitting "Item not found."
• Team mode & Auto Pair: join a 16-developer team (15 testers, a 3-tester buffer above the 12-tester requirement) or match 1:1 at your own pace.
• On-device install verification: zero screenshots. BetaLobby confirms installs directly on the device.
• Daily check-ins & TRUST: installing once isn't enough. BetaLobby tracks daily check-ins (actually opening the apps across the 14 days) with push reminders, backed by a 100-point TRUST score that penalizes freeloaders and early dropouts.
BetaLobby is completely free, no paid plans. Built by an indie dev for indie devs.
What was the hardest part of your own closed test? I'd love to hear it.