We buy apple enterprise account for in-house app distribution.
In an app after several weeks of continuous development and multiple versions after rapid internal iteration, when we need to release this to our actual application scenario, face our real users to say hi, if their products before release (beta version) did find some potential cut relatively stable seed users, you should often hear users complain about problems.
It tends to focus on the following points: Are my needs really being addressed?
Is the versioning process complex?
Is the release responsive enough?
In fact, for application distribution, the iOS platform has made full consideration for different usage scenarios, which directly reflects different account types.
The Apple Developer Program has four account types: Individual, Corporate, Enterprise, and Educational Developer.
Personal developer accounts are probably the most common, costing $99 a year, and can only display a personal ID on the App Store.
And personal accounts can only have one developer and 100 Apple iOS devices tested for UDID.
So if your app is going to be tormented, 100 UDIs is a pretty small amount of money.
In order to adapt to different usage scenarios, Apple offers four different ways to distribute apps: App Store, Volume Purchase Program, In-house Enterprise App, and Ad Hoc App.
I'll leave the first two out of the question. I'll focus on in-house enterprise app publishing and Ad Hoc.
In-house app can't be submitted to the App Store, and Apple doesn't have to approve the
content of an in-house app to be released.
There is also no current limit on the number of devices to be installed for in-house app.
So the authority is the most open, suitable for supporting the open mass testing of external users.
So you see a lot of third party open channel download IPA is actually based on other corporate accounts to support.
Of course, compared to the in-house open testing method, Apple also supports Ad Hoc distribution of apps to facilitate in-house app developers to test their apps on real machines. The specific content of the apps does not need to be reviewed by Apple, but it limits the distribution of each app to more than 100 devices.
This is a good way to release an enterprise application if the application needs to be tested on a small scale or if the enterprise is small.
In-house app release process
Select In-House and Ad Hoc, and click Continue.
Note that if an in-house certificate has already been created, it cannot be created again, and this option will be grayed out, as shown In the figure below.
If you want to recreate it, you can Revoke the certificate pf in-house app in the previous list.
Create Certificate [Via by Chenkai]
Click New to go to the next step. You need to upload a certificate. In Mac system, go to "Keychain Access" and select "Keychain Access" - "Certificate Assistant" - "Request Certificate from Certificate Authority".
Log in to the Enterprise Account Member Center and create a certificate in Certificate-Production.