Our first BetaLobby team is full ๐ 16/16!
16 indie Android devs from around the world, installing each other's apps right now to get through Google Play's closed testing (12 testers / 14 days) together.
#AndroidDev#IndieDev#buildinpublic
14/16 ๐ Our first BetaLobby team is almost full. 2 spots left!
Free test-for-test for Android devs going through 12 testers 14 days closed testing. One shared group, installs verified automatically, no daily screenshots.
https://t.co/9Yjl3deq28
#AndroidDev#buildinpublic
@WealthSamrat Easy ๐
1. Join the group: https://t.co/E4cwE7J1Jt
2. [email protected] as a tester group
2. Install BetaLobby on Play: https://t.co/RsEw8dJfW1
Submit your app and join the team (12/16)
Takes a few minutes, I'll help if you get stuck!
@KhanjanKavani in ๐ happy to test both!
Btw I built BetaLobby, a free T4T app. If you use Google Groups, add [email protected] next to yours and join a team, everyone in it tests your app ๐
@DaniloG76442396 Installed & playing. Really fun! ๐Only issue: frame drops when bosses spawn and fish pile up.
Since you use a Google Group, add [email protected] next to yours (current testers stay), then join a team in BetaLobby. We're 12/16, everyone tests Rogue Fish
I used to see Google's 12 testers / 14 days rule as pure friction.
Then my own closed test started surfacing real problems:
โข a tester kept failing because adding a Google Group needs a review
โข another hit a group sync delay I'd never noticed
Fixed all three this week.
@DaniloG76442396 Followed! Heads up: Rogue Fish says "not available in your country" for me.
Closed testing has its own Countries/regions setting, separate from production, so you can safely enable all there. More testers can join that way.
@mudassar6969@GooglePlayBiz No way to skip the 14 days, but the 12 testers part can be easy. I built BetaLobby, where devs test each other's apps. Our first team is 11/16, join and the whole team opts in at once ๐ https://t.co/9Yjl3deq28
@DaniloG76442396 Rogue Fish looks awesome, just requested to join the group
Do you need more testers? I built BetaLobby: devs test each other's apps for 14 days. Our team is 11/16, join and everyone installs & tests yours ๐ https://t.co/9Yjl3deq28
@cdesclo Congrats on shipping! Saw you're at 11/12, happy to be your #12 if you drop your opt-in link.
I'm in closed testing too, so a swap would really help me as well.๐
Biggest fix today: if your app isn't visible yet because Google is still reviewing your tester list, BetaLobby now checks every 20 min and pings you the moment it's ready.
No more refreshing Play Console ๐
#buildinpublic#indiedev
The fix: kill the duplicate daemon, add a maintenance mode to my watchdog script, and write a deploy script so I stop racing my own cron job.
Lesson: if something feels haunted, check ps for a second daemon.
My backend went down today right as a tester was signing in ๐
Root cause: my server had TWO Docker daemons running two identical copies of my whole stack, and both PocketBase instances were writing to the same SQLite file.
#buildinpublic#indiedev
@Joshua_WD Thanks Josh! Basically this screen ๐
โข Check-in launches the app you're testing and only counts once you've opened it
โข 14-day grid + 4 โค๏ธ as "lives" (10/14 to pass, or your TRUST score drops)
โข Every tester is a dev who needs testers too: you keep mine open, I keep yours
Finding 12 testers for Google Play's 14-day closed testing is tough for solo devs.
Got tired of asking around on Reddit, so I built BetaLobby: a free tool for indie Android devs to team up & auto cross-test apps.
Link in reply ๐
#Android#IndieDev#GooglePlay
@justjoemer The closed testing rule really is the biggest headache. I was in your exact shoes recently, so I built https://t.co/9Yjl3deq28 โ a free platform where indie devs team up to cross-test each other's apps for the full 14 days.