3 weeks ago
44 ARTICLE AD
Alongside the Apple Intelligence-powered iOS 18 updates for consumers and developers, Apple is rolling out a sizable refresh to its app testing platform for developers, TestFlight. Developers will have more control over who can join their beta and how an app’s new features are shared with testers. They’ll also be able to view metrics related to the beta’s success, in terms of how many people viewed the invite and opted in, and why others did not.
The changes will make it easier for developers to target their betas and gain more feedback ahead of their app’s public debut on the App Store. Meanwhile, for beta testers, the redesigned invitations will offer more information about the app, helping them make a decision as to whether or not they want to join the test group.
With the update,invitations now highlight new features or content coming to the app or game, which could encourage testers to try it out. In addition, Apple says the beta builds of apps and games that have been already approved for publication the App Store will be able to include screenshots and the app category along with their invite. This will make the beta testing experience feel more like downloading from the App Store. It could also challenge the alternative testing marketplaces that have popped up in recent years, like Airport, which includes app screenshots, and Departures, which organizes apps into categories.
The ability to set criteria for TestFlight testing, meanwhile, helps developers narrow their test groups to specific audiences, like those using a particular device type or OS version. Given that TestFlight offers a max of 10,000 invitations, this could help save spots in a more popular beta from going to those who can’t yet use the app on their device or aren’t a part of the intended audience for the test. Developers can set a maximum number of testers in the group, to further control access.
The new invites will also be sent out from a new public link that will include new metrics like how many testers viewed the invite and then chose to accept it. Developers will be able to see how many potential testers didn’t meet the criteria they set, as well. Users, meanwhile, will be able to leave feedback for the developer, to help them understand why they didn’t join the beta for other reasons.
Sarah has worked as a reporter for TechCrunch since August 2011. She joined the company after having previously spent over three years at ReadWriteWeb. Prior to her work as a reporter, Sarah worked in I.T. across a number of industries, including banking, retail and software.
Subscribe for the industry’s biggest tech news
