[afternooner]

Enterprise and government comes with a lot of baggage that no sane developer would ever try to take on. You are manifesting your priorities on them, and that simply may not be the case. The $200 price point is likely that high in order to keep the client base low. I'm not saying you're wrong, but Apple itself barely supports enterprise with most of their enterprise management bits being third party. A laptop without a docking station??? Crazy, they might as well not sell computers...

Source: Work for government, not entirely sane, have had Apple reps brought in to discuss in house dev, written in house application, ruby, C#, C, Obj-C, JS, C++ developer in order of preference.

[danielsju6]

On iOS "enterprise provisioning" means less baggage. No UDIDs, which are deprecated in software BTW. To be clear this is a tiny patch that adds support for some 40%+ of dev shops and all enterprises. All we are talking about is this:

  unless App.config.provisions_all_devices? || App.config.provisioned_devices.include?(device_id)
    App.fail "Device ID `#{device_id}' not provisioned in profile `#{App.config.provisioning_profile}'"
  end

Where the provisions all devices is my bit supported by a single line helper, it's not scary. If you have more than 100 devices beta testing your app you use enterprise provisioning PERIOD, it doesn't have anything to do with classic "enterprise" except you need a DUNs and to pay Apple an extra $100/year.

Almost every dev shop that is more than two guys I know uses this.