App Distribution: From Ad Hoc to Enterprise
By Nimrah Bilal · · 4 min read
Ad Hoc distribution is for testing an iOS app on a limited set of registered devices. Enterprise distribution, through the Apple Developer Enterprise Program, is for an eligible organization to deploy its own apps to its own employees without registering devices. Between them sit TestFlight, the App Store and custom apps through Apple Business Manager. This guide compares the options and explains what changes when a team outgrows Ad Hoc.
The main iOS distribution methods
| Ad Hoc | App Store | Enterprise (in-house) | |
|---|---|---|---|
| Purpose | Testing and previews on known devices | Public release | Internal apps for an organization's employees |
| Apple program | Apple Developer Program | Apple Developer Program | Apple Developer Enterprise Program (separate, restricted eligibility) |
| Device registration | Yes, up to 100 per device type per year | No | No |
| Apple review | No | Yes | No |
| How users install | Link (OTA) or cable | App Store | Link (OTA) or MDM |
| Main limitation | Device limit, rebuild for new devices | Review, store rules | Employees only, Apple can revoke the certificate if misused |
Ad Hoc distribution
An Ad Hoc build is signed with a provisioning profile listing the UDIDs of allowed devices. It is the fastest way to get a build to a few testers or a client: no review, install from a link. The trade offs are the device limit, the need to rebuild whenever a device is added, and profile and certificate expiry. See Ad Hoc distribution challenges.
Enterprise distribution
The Apple Developer Enterprise Program lets a qualifying organization sign apps for internal use by its employees. Devices do not need to be registered and there is no App Review. On first launch, users must trust the organization's developer certificate in Settings under VPN and Device Management, unless the app is installed through MDM.
Apple is strict about this program. Eligibility is limited, the apps may only be used by the organization's own employees, and Apple can revoke an enterprise certificate if it is used to distribute to customers or the public. A revoked certificate stops every app signed with it. Check Apple's current program requirements before planning around it.
Other options teams often move to
- TestFlight: for larger beta groups. No device registration, testers install through the TestFlight app, external testers need a beta review, and builds expire after 90 days.
- Custom apps through Apple Business Manager: private apps for specific businesses or schools, delivered through the App Store infrastructure after App Review. This is Apple's recommended route for many business to business apps that are not purely internal.
- MDM: organizations that manage employee devices often deploy apps through their mobile device management system.
Challenges when moving from Ad Hoc to Enterprise
Eligibility and legal setup
Enterprise membership is for organizations, not individuals, and Apple verifies the organization. Plan time for the enrollment and confirm the program fits your use case. If the app is for customers or partners, Enterprise is the wrong tool.
Certificate and profile management
Enterprise distribution certificates and profiles expire and must be renewed, and every app signed with an expiring certificate needs a new build. Keep a calendar and a clear owner for signing assets.
Access control
Without UDID registration, anyone with the file could install an Enterprise build. You need another way to make sure only employees get it: an MDM, a private internal portal, or password protected links that only staff receive.
Updates
Enterprise apps do not update through the App Store. Users install each new version from your distribution channel or receive it through MDM, so make sure they know when a new build is out.
Where AppForShare fits
AppForShare hosts signed iOS builds (Ad Hoc, Development or Enterprise) and Android .apk files, and gives each build an install link and QR code for over the air install.
- Ad Hoc testing: collect UDIDs with the free UDID finder, then share each new build by link.
- Internal Enterprise builds: share with password protected links. On Team, private projects only open for invited testers, invited testers are emailed when a new build is uploaded, and you can see who installed.
- Your own branding: Team includes a custom domain for install links and a white-label install page.
AppForShare does not provide Apple certificates, does not sign or re-sign builds and is not an MDM. You remain responsible for following Apple's program rules. Plan details are on the pricing page.
Frequently asked questions
What is the difference between Ad Hoc and Enterprise distribution?
Ad Hoc builds install only on devices registered by UDID, up to 100 per device type per year, and are meant for testing. Enterprise builds, from the Apple Developer Enterprise Program, install on any device without registration but may only be used by the organization's own employees.
Can I use an Enterprise certificate to share an app with customers?
No. Apple only allows Enterprise distribution to an organization's own employees and can revoke the certificate if it is misused. For customers, use the App Store, TestFlight or custom apps through Apple Business Manager.
Can AppForShare host Enterprise signed iOS apps?
Yes. AppForShare accepts iOS builds signed Ad Hoc, Development or Enterprise and gives each one an install link. It does not provide certificates or sign apps.
Do Enterprise apps need device UDIDs?
No. Enterprise builds do not require device registration. Users trust the organization's certificate in Settings the first time they open the app, unless it is installed through MDM.
