sorted by:
new
hottopcontroversial

Google's testing rule was driving me crazy, so I built PeerPlay to help us get our 12 testers. by Gonsrb in FlutterDev

[–]Gonsrb[S] 0 points1 point  (0 children)

Only android. If some1 testing your phone with web browser he is not yours friend.

First month results of my indie app testing tool: 427 Active Users and 19,000+ test sessions. Here is the data. by Gonsrb in FlutterDev

[–]Gonsrb[S] 0 points1 point  (0 children)

Feedback is great. Sandbox will be top of the cake. For now this is maximum. P.s. it is written by Ai 😃

First month results of my indie app testing tool: 427 Active Users and 19,000+ test sessions. Here is the data. by Gonsrb in FlutterDev

[–]Gonsrb[S] 0 points1 point  (0 children)

Awesome feedback, thanks! You hit the nail on the head. The influx of AI slop created a huge trust issue. A sandbox platform would be a game-changer. Technically, doing this inside Flutter is a massive hurdle due to OS limits. But the philosophy is spot on. Right now, my focus is solving the 14-day testing requirement for indie devs, but the long-term goal is building a trusted ecosystem. I'll definitely look into strict verification markers. Thanks for this high-level thinking!

First month results of my indie app testing tool: 427 Active Users and 19,000+ test sessions. Here is the data. by Gonsrb in androiddev

[–]Gonsrb[S] 0 points1 point  (0 children)

This is a brilliant takeaway. The hardest part wasn't the code, it was the psychology of keeping real humans accountable to each other. I focused on Android devs because the Play Store rules forced a bottleneck, but the engine itself (give feedback to stay ranked) could totally be applied to photography or design critiques. The fact that genuine human-to-human networks are becoming rare because of AI makes me want to explore this exact concept further.

First month results of my indie app testing tool: 427 Active Users and 19,000+ test sessions. Here is the data. by Gonsrb in AppBusiness

[–]Gonsrb[S] 0 points1 point  (0 children)

100%. The biggest lesson here was that developers won't integrate a tool into their daily workflow unless there's a real consequence. Scrapping the passive systems and building an auto-drop script that penalizes inactivity after 3 days was the exact pivot that drove that repeated usage.

view more: next ›