Applivery supports both Enterprise (in-house) and Ad-Hoc signed iOS apps.
Sometimes it is difficult to understand which are the differences, requirements and limitations between both signing methods so below we are providing a comparison table that will help you get a bit more familiar with them.
Note
Please note that these lines below do not depend on us (Applivery) and might change at any time without any notice.
| Profile type | Limitations | Expiration | Apple Cost / year |
|---|---|---|---|
| Ad-hoc |
– App distribution to a restricted set of specific devices. – Requires creation of a provisioning profile containing the UDIDs. – Users: 100 devices |
Certificate: 3 years Apps: 1 year |
99 USD / year (Read more) |
| Enterprise (In-house) | – Users: Unlimited, as long as they are employees or collaborators of the organization |
Certificate: 3 years Apps: 1 year |
299 USD / year Application needed (Read more) |
As you can see, in most cases Ad-hoc can serve all your needs, knowing that you will have to collect end-users devices UDIDs and add them to your provisioning profile before signing the App. If you are looking for a more wide and massive distribution within an organization, most probably you will have to go for the Enterprise (In-House) certificate.
We highly encourage you to read more about it at Apple’s website.
Note
Please note that the App Store signing type is different from Ad-Hoc and Enterprise signing. The App Store signing type is exclusively for apps meant to be released through the official App Store. It cannot be utilized on Applivery's platform as MDM systems are designed to manage and deploy enterprise apps, not apps intended for public distribution on the App Store.
