Short answer: sign the build with an ad hoc provisioning profile that lists the tester's iPhone, host the IPA behind an HTTPS install link, and send the link. If the tester only needs to see and tap through the app, share a simulator in their browser instead, which needs no device registration at all.
TestFlight is the right tool for most beta testing. It is also slow for the first external build, because that build goes through Beta App Review, and every tester needs the TestFlight app and an invitation. When you want a build on someone's phone in the next five minutes, these are the options.
Option 1: an ad hoc build with an install link
An ad hoc build is signed with a distribution certificate and a provisioning profile that lists specific devices. Any iPhone on that list can install the IPA directly.
- Register the device. Add the tester's device identifier (UDID) under Devices in your Apple Developer account. An account can register up to 100 devices of each type per membership year, and removing a device does not give the slot back until renewal.
- Create an ad hoc provisioning profile for your app ID that includes the device, and archive the app with it. In Xcode: Product › Archive, then Distribute App › Release Testing (called Ad Hoc in older versions).
- Host the IPA and a manifest. iOS installs over the air from an
itms-services://link that points to a small manifest file. Both the manifest and the IPA must be served over HTTPS. - Send the link. The tester opens it in Safari on the iPhone and confirms the install.
The fiddly parts are collecting UDIDs, rebuilding when a new device is added, and hosting the files. Tools exist to take those away. In VenelX Studio, any build on your Mac becomes an install page with a QR code; you choose whether it is for your team, anyone with a passcode or anyone, and set an expiry and a download limit.
Option 2: share a simulator instead of a build
Many "can you look at this?" requests do not need a real phone. A designer checking spacing or a client approving a flow can use a simulator running on your Mac from their own browser. Nothing is installed, no UDID is registered, and it works for people on Windows or Android.
This is not a substitute for testing on hardware: cameras, Bluetooth, performance and push delivery behave differently on a simulator. For review and demos it is the fastest route. See how to share an iOS simulator in the browser.
Option 3: in-house and custom app distribution
Large organisations have two more routes. The Apple Developer Enterprise Program lets a company install internal apps on employee devices without listing UDIDs, but Apple only accepts organisations that meet its eligibility rules, and it must not be used for customers or the public. Custom Apps through Apple Business Manager distribute a privately listed App Store app to specific organisations. Neither is a quick way to send a beta to a few testers.
Which one should you use?
| You want to | Use |
|---|---|
| Put a build on a few known iPhones today | Ad hoc build + install link |
| Let someone click through the app right now | Shared simulator |
| Run a beta with hundreds or thousands of people | TestFlight (up to 10,000 external testers) |
| Give every employee an internal app | Enterprise or Custom Apps |
When TestFlight is still the answer
Use TestFlight when testers are not people you know individually, when you need more than 100 devices, or when you want crash reports and feedback collected for you. Internal TestFlight testers, who are members of your App Store Connect team, get builds without Beta App Review, which makes it quick for the core team. TestFlight builds stop working after 90 days.
A common setup is both: ad hoc links and shared simulators during the day for quick checks, and TestFlight for each release candidate. Uploading to TestFlight from your own Mac covers the second half.