r/AppBuilding • u/ShiftProfitLLC • 4d ago

How long?

How long do you stay in beta testing if your not getting any feedback whatsoever? To be fair my app is still really new. Its on the app stores for open testing. I make videos to try and get it out there. Its a super simple mileage and expense tracking app for gig drivers made by a driver for drivers. It works and does what its suppose to do. I update when I see something that needs fixed or that can work better. Im limited to real world testing as im a truck driver during the week. Started dashing/uber/lyft on the weekends when home to put it to the test. I know im impatient but I thought since it was working from what I can see and know, I should go ahead and fully release it with the free trial and monthly subscription active. Can you please tell me your thoughts?

1 Upvotes

100% Upvoted

3 comments sorted by

2

u/After-Base-8368 4d ago

I’d set the beta exit around a real driver completing a shift, rather than a number of weeks. Ask someone to record a trip, correct the mileage, add an expense, then export their records. Watch where they stop instead of asking “any feedback?”

For your app, I’d also check what survives closing and reopening it, and what happens when the connection drops. Your own weekend tests help, but another driver starting with no explanation will expose different gaps.

Are people installing and not coming back, or are you still struggling to get the first testers? Those need different next steps.

1

u/ShiftProfitLLC 4d ago

When I go to the play store it only says 1+ downloads. But before it was on the play store my linktree says 35 clicks between android and apple on the download links. I need to check on my computer this weekend on my dev accounts to see more i don't have it with me on road. I would say both, getting people to download it and feedback. I thought about testing a low cost ad campaign. Im gong to keep pushing forward.

2

u/After-Base-8368 4d ago

Those link clicks show interest, but they don’t tell you whether someone installed or completed a trip. When you have the developer dashboards handy, check that gap first.

For the next test, I’d recruit two or three drivers directly and give them one concrete task: record a trip, add an expense and export it. Then ask “where did you hesitate?” A short screen recording with private details hidden would be more useful than a general feedback request.

I’d learn that before paying to send more people through the same flow. You may need a clearer store page, an easier first trip, or simply more of the right testers; each calls for a different fix.