Feedback on my first public TestFlight beta (iOS 26 car-collection app)

Question

Created 6d

Replies 1

Boosts 0

Participants 2

Hi everyone,

I'm an independent developer and designer, and I've just opened my first public TestFlight beta for an app called Paddock. It's an iOS 26 app to keep track of your cars: maintenance, fuel costs, wheel sets and history, with the data stored on the device.

I'm still learning how to run a beta well, so I'd really value advice from people who've been through this:

Testers. What worked best for you to find real testers (public link, groups, communities)? How did you keep them engaged after the first install?

Feedback. How do you collect it so it's useful? Do you rely on TestFlight feedback, a form, email? Is there something you wish you had asked from the start?

What to Test and onboarding. What do you put in the beta description and the test notes so testers know what to try without feeling like it's homework?

Builds. Any tips for pacing builds and keeping the 90-day expiry from catching you off guard?

Beta App Review. Anything that tends to trip up first-time submissions?

If you'd like to try it and tell me what feels off, the beta is here:

https://testflight.apple.com/join/qup6rF31

It needs iOS 26. Honest criticism is the most useful thing you can give me.

Thanks for reading, and for any advice.

Arturo

Answer 1 · 1d

Pokpong OP

1d

I would start with a small group of people who actually use cars day to day, rather than chasing lots of installs. A local car-owner group or a community for people who track maintenance is more likely to give you useful feedback than a general app-testing group. A public link is convenient, and you can add device or OS criteria and cap the number of testers while you learn what works.

For the first round, give testers two or three real things to try, such as adding a vehicle, logging a fill-up, and finding the next service date. Keep the What to Test notes short and ask where they got confused, not just whether they liked it. TestFlight screenshot feedback is a good place to start. A simple form can help if you want structured answers, but I would avoid asking people to fill out both unless there is a reason.

I would send a short note when a new build is ready saying what changed and what you want them to check. That gives people a reason to come back without making every build feel like homework. For the 90-day limit, set a calendar reminder a couple of weeks before expiry and upload a new build when there is something worth testing. The first build sent to external testers needs TestFlight review, so it is worth submitting that early.