Enterprise madness: Untrusted Enterprise Developer, Untrusted apps and MDMs

It is only one dialog for the developer, not per app.

We had this setting before - represented as alertview asking if u trust. Not much difference, aside that you see where an specific app belong to.

However I agree with the wording. "Untrusted" is suggestive and needs to be reworked. A person installing an enterprise app is doing this for a reason. Suggesting that it is unsecure is perhaps suitable for user that use apps from Apples App-Store, but not for Inhouse distribution.

Frankly: as a matter of fact we trust our Inhouse developers more than Apple - so this dialog should pop up for Apple own apps but not for our apps.

I disagree - the problem for my location will not be the fact that the cert needs to be OK'd, but that instead of a popup appearing asking the user if he trusts the app with a 'YES', 'NO', a popup appears telling the user he must OK the app in settings. For an app with 3000+ users, many of whom aren't necessarily computer savvy nor may not use iOS on a daily basis, it's a non-starter asking them to go into settings and 'OK' an app as well as the developer.

I'm having trouble believeing that Apple really wants to increase their enterprise footprint with stuff like this. It's kinda like there's no grownups in charge.

Apple's done this because they want to discourage the use of enterprise certs as a mechanism for distribution. Enterprise iOS is getting a bit like Windows Vista; by all means tighten up communications, but don't make enterprise distribution more difficult than it already is.

Just to add another perspective, the additional requirement that "All users who install your app for the first time will need an internet connection" in iOS9 certainly was never vetted against an entire class of apps that live within the military/government communities of interest. Many of these devices may NEVER have internet access, and thus requiring internet access will basically make the app (and hence the justification for device's procurement) unusable and force organizations to look at other platforms.

I completely agree. This is an underhanded way to kill Enterprise app distribution. We paid the $300 enterprise developer license expressly to be able to distribute custom apps this way. Our clients have very specific app requirements and do not want their custom apps on the App Store. Requirements change quickly and we were able to respond to their needs with very quick fixes and updates; going through Apple approval process would kill our response times. Their end users are not tech savvy and this new multi-step-digging-into-settings trust issue is a huge barrier to app adoption.

MDM is not an option for these custom apps. Our clients range from those that simply do not have the infrastructure to require their users to adopt MDM, or they already have an MDM that is managed by another corporate entity they have no control over (devices cannot belong to more than one MDM).

We've looked at the iOS B2B distribution method, but the end users are an undetermined mix of iOS, Android, and Windows Phone users. Need to be able to send a link to potential users, which either presents them with a choice of install links for different platforms or auto-detects their platform and forwards to appropriate install. B2B app distribution also requires the Apple approval process.

MAM and Enterprise App Store solutions like Apperian are overkill and cost-prohibitive to offer one custom app for a given client -- and I believe they will have this same Untrusted Developer issue with iOS 9 if you are distributing an enterprise app.

Apple needs to restore the ability to link off of the "Untrusted Developer" dialog to allow the app to run. And please change the wording (agree with Helge) -- "Unverified" perhaps instead of "Untrusted"? Indicating the app has not been verified by Apple, but app is requesting permission to run.

The current dialog does not even give instructions on how to change the settings. Even tech savvy users have to google to figure it out. Unacceptable.

You do realize that an Enterprise License is for app distribution within your own company; i.e., your employees.

Distributing apps to other companies in the manner you are using is a violation of the Enterprise license.

Each of your client companies must have their own Enterprise License and all that entails.

Completely agree. Many of my clients do have their own enterprise accounts, but this iOS 9 change is turning their deployments upside down. Espeically when they also have another platform to compare against that installs wthout requiring the user to manually go into Settings. I understand the reasoning behind this and I appreciate the concern for security (unlike other platforms), but this isn't the right solution. The alert should have a Trust option plain and simple.