Enterprise in-house or regular program with ad hoc (attention newbie)

> the right apple program, app type and a good workflow for the future.

Then an Enterprise Program is the proper direction.

If you stick with ad hoc, then all those employee devices must remain associated with your developer account and will forever count against your 100 device per year limit. If you revoke your distribution certificate at any point, or when it expires normally each year, the app will stop working and will need an update. I guess enterprise certificates eventually expire requiring an app update too, but I'm not sure if it's just one year.

Those are the practical considerations. I don't know about the legal side.

Enterprise certificates are 3 years, provisioning profiles 1 year. I think MDM systems can just push a new profile, but if you use OTA deployment you rebuild the app with the new profile and each user installs the new version of the app over the old one.

Thanks for yours answers.

So it seems, that i really need this enterprise programm.. Too bad...

When there is no need to collect the UDIDs for an in-house app - how does it works? Who can i prevent unauthorised app installs?

Sebastian :-)

What do you mean 'too bad'? What happened to doing the right thing the right way?

It is the responsibility of the company that gets the Enterprise Developer account to make sure that unauthorized app installs don't occur. There are 2 options.

1. Use an MDM system, such as Profile Manager on OS X Server or a third-party MDM system.

2. Design a web site with proper authentication so only authorized users can do an OTA (over the air) installation. I think there also may be third-party "app store" packages to accomplish this.

You should definitely use a third party solution because you don't want to manage the update cycle of the application as it will expire every year. Also if you fix bugs or crashes you will need your users to update the application on their devices and I have found than using a third party solution works best.

Apple's MDM works fine if you need an MDM solution but if you are not part of the company the company won't allow you to enroll the employees devices.

You then have two choices :

Third party BYOD solution or create your own website with authentication to restrict download of the application. However by creating your own website you will have to take care of the lifecycle of the application (new release, signature expiration ...). You will have to inform users to update the application when there is a new release or when the app is close to its expiration date.