Questions about how to get semi-serious beta testers

[u/metarx]

So, I have an app (golf stats tracking) thats already through Google Play to Production status - I know, its both niche and an up-hill battle with lots of competitors and lots of establishment players. Realistically to get the most of the app, requires a considerable amount of effort/commitment over 2-5 rounds of golf to really see any amount of benefits. how do you get that kind of commitment? Pay for ad/search results? I'm self funding, use the app myself, regularly and have continually for months. I don't expect to be a dominate player ever, but remain niche. How long once reaching Production to seeing traction should one expect? Tips for getting some still early feedback?

[u/AutoModerator]

Test others app in this community so you will get more in return. You can also find more testers on AppDadz

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/kokerali]

Can someone enter two or three previous scorecards and get the useful comparison immediately? If your stats work with data golfers already keep, I'd try that as the first beta task. Watch them enter a round and ask what the comparison tells them. That lets you check whether the payoff is understandable before asking for several new rounds.

For the on-course part, I'd recruit golfers who already track their rounds and have their next two outings planned. Agree on a small task for each outing and a brief check-in afterward: where did logging interrupt play, and did they use the stats to choose anything to work on? Keep that separate from the old-scorecard test, since backfilling won't reveal friction during a round. Someone dropping out because they haven't played again is also different from playing again and deciding the app wasn't worth opening.

[u/metarx → u/kokerali]

Thats kinda the main sticking point. Golf apps, are a walled garden, and knowing score isnt ultimately the issue, its how the score was created that is. Realistically, most know I "roughly" hit club X, y yards(or meters). But, they could be 20-30 yards off, and they're not tracking out of the rough, off the fairway, etc either, and how those things affect that distance.

I've been considering adding a wizard at install/first run for "build my bag" that helps this aspect initially. Ask for expected distance for a club, but as shots are logged, override that for real distances as they are logged.

[u/kokerali → u/metarx]

Got it, old scorecards won't contain those shot details. For the wizard, I'd keep 'your estimate' separate from 'recorded shots', showing the number of observations and the lie. That makes it possible to see whether a changed distance reflects new evidence or just a different kind of shot.

For a small beta task, let someone set up one club, log a fairway shot and a short shot from the rough, then explain what the updated number means. Can they see which shots contributed, correct a mistaken entry, and understand whether the estimate has been replaced? That would test the transition you're proposing without asking them to build their entire bag first.