Alongside the iOS 18 update for consumers and developers powered by Apple Intelligence, Apple is rolling out a major update to TestFlight, its app testing platform for developers. Developers will have more control over who can participate in betas and how new features in their apps are shared with testers. You'll also be able to see metrics related to your beta's success, such as how many people viewed your invite and opted in, and why others didn't.
This change will make it easier for developers to target beta versions and get more feedback before their apps' public debut on the App Store. Meanwhile, for beta testers, the redesigned invitation provides more information about the app to help them decide whether to join the testing group.
The update will allow invitations to highlight new features and content added to your app or game, potentially enticing testers to try it out. Additionally, Apple says beta versions of apps and games that have already been approved for publication on the App Store can include screenshots and app categories in their invitations. This makes the beta testing experience similar to downloading from the App Store. It could also take on alternative testing marketplaces that have emerged in recent years, such as Airport, which includes app screenshots, and Departure, which organizes apps into categories.
On the other hand, the ability to set criteria for TestFlight tests helps developers target test groups to specific audiences, such as those using specific device types or OS versions. Given that TestFlight offers up to 10,000 invitations, this is a more popular beta spot for those who don't yet have the app on their device or are not in the test audience. may help prevent you from being assigned. Developers can set a maximum number of testers in a group to further control access.
New invitations will also be sent from the new public link. This link includes new metrics such as the number of testers who viewed the invitation and chose to accept. Developers can also see how many potential testers failed to meet the criteria they set. Meanwhile, users can leave feedback to the developers to understand why they did not participate in the beta for other reasons.