Last year Apple bought TestFlight, the popular beta distribution app, and relaunched it WWDC 2014 in a more focused, integrated form, but one that also required App Store approval for major feature changes. Since then developers and testers alike have been trying it out. The verdict so far? Supertop really likesit:
None of these issues come close to negating the benefits of TestFlight for us as we work on updates Castro and Unread. We'll be excited to beta test Castro 2 this way as well. App developers should take the time to try it. The availability of a much larger test audience, far better install rates and simplified IAP testing should help you release higher quality apps on the store.
In the past few months, I've been testing about 50 apps with TestFlight, and, as a user, I think the system is way better than the old days of beta testing with Hockey and the original TestFlight. I don't need to give developers my device UDIDs; all my betas are in the TestFlight app; I get notifications for updates; and, I can easily unlock In-App Purchases in beta builds with my Apple ID. Apple has built the new TestFlight with simplicity in mind, and I appreciate the time it has saved me so far.
I'm apparently not testing anywhere nearly as many betas as Ticci — hey, devs! — but the ones I have been testing have worked really well, and for exactly the reasons he states.
Hopefully crash reporting and other useful features are in the pipeline.