The latest articles on DEV Community by Hameed Ur Rehman (@hameedurrehman). https://dev.to/hameedurrehman https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1299337%2Fe797f520-6286-4402-86f7-ed082e4e208b.jpg https://dev.to/hameedurrehman en Hameed Ur Rehman Wed, 12 Aug 2026 03:50:33 +0000 https://dev.to/hameedurrehman/ad-hoc-distribution-vs-testflight-in-react-native-a-practical-comparison-1nid https://dev.to/hameedurrehman/ad-hoc-distribution-vs-testflight-in-react-native-a-practical-comparison-1nid <p>If you're testing an iOS build with real devices, you've got two main paths: Apple's TestFlight, or Expo's EAS Preview using Ad-Hoc provisioning. They solve the same problem — getting a build onto a real iPhone without the App Store — but the workflows are genuinely different, not just cosmetically.</p> <h2> How each one works </h2> <p>TestFlight uses Apple's official infrastructure. You upload your build to App Store Connect (often via npx testflight to speed this up), Apple processes/reviews it, and testers install the TestFlight app and accept an email or public link invite. No UDID collection needed — Apple handles device registration behind the scenes.</p> <p>Expo EAS Preview (Ad-Hoc) uses Ad-Hoc provisioning. You register each tester's device UDID against your Apple Developer account before building — either manually (eas device:create, eas device:list) or by having the tester scan a QR code that installs a temporary profile. Once devices are tied to your provisioning profile, you build with:</p> <p>bash<br> <code>eas build --platform ios --profile preview</code></p> <p>This generates a direct install link/QR code — no App Store account or TestFlight app required.</p> <h2> Comparison table </h2> <p>Feature Expo Preview / Ad-Hoc Apple TestFlight<br> Device limit ~100 devices/device class/year (Apple Developer account tier) Up to 10,000 external testers<br> Processing time Immediate after cloud build finishes Apple review/processing (mins to hours)<br> UDID management Manual or profile-based registration required Not required, handled by Apple<br> Best for Fast internal testing, client demos, strict ad-hoc distribution Larger-scale beta testing, staging before production</p> <p>Which one should you use?<br> Fast internal iteration, client demos, small teams → Ad-Hoc. No waiting on Apple, instant install links.<br> Wider beta testing before a production release → TestFlight. Built-in scale, no manual device management.</p> <p>Most teams I've worked with end up using both at different stages: Ad-Hoc during active development for quick feedback loops, TestFlight once the build is stable enough for a broader external beta.</p> <p>Curious what others are using — drop your setup in the comments.</p> ios mobile reactnative testing