9 added 105 characters in body
source | link

A: FullSolo Enterprise

  • How it works: You have one public Appexchange listing. Each customer installs your package into their org. You brand an iOS app for each customer, build the app, and send them an unsigned binary. Each customer uses their own Apple Dev account to sign the app for their users (100 max devices) or their own Enterprise account (no device limit).
  • How it ends: Ongoing pain. Additional costs with codesigning, perhaps the least enjoyable part of iOS development, and now you have to teach your customer how to do it? Additional time and $ for your customer. You buy some Excedrin.

A: Full Enterprise

  • How it works: You have one public Appexchange listing. Each customer installs your package into their org. You brand an iOS app for each customer, build the app, and send them an unsigned binary. Each customer uses their own Apple Dev account to sign the app for their users (100 max devices) or their own Enterprise account (no device limit).
  • How it ends: Ongoing pain. Additional costs of time and $ for your customer. You buy some Excedrin.

A: Solo Enterprise

  • How it works: You have one public Appexchange listing. Each customer installs your package into their org. You brand an iOS app for each customer, build the app, and send them an unsigned binary. Each customer uses their own Apple Dev account to sign the app for their users (100 max devices) or their own Enterprise account (no device limit).
  • How it ends: Ongoing pain with codesigning, perhaps the least enjoyable part of iOS development, and now you have to teach your customer how to do it? Additional time and $ for your customer. You buy some Excedrin.
8 added 9 characters in body
source | link

Option A: Full Enterprise

Option B: You Have No Chance To Survive Collect Your UDIDs

Option C: Public

You cannot use an Appexchange listing to host an IPA file. You need generic file storage (I've used S3 for this) and an installation page your users can access on their devices.

Edit the second: There is one additional overwhelming advantage that is unique to Option C: all of your users receive updates simultaneously and can update without waiting on their admin to distribute your IPA to them... unless, of course, you are hosting the IPA file yourself and built your own app updating and notification mechanisms. (You did? STEP BACK FROM THE EDGE!!!STEP BACK FROM THE EDGE!!!)

Option C might be ruled out if you are using private APIs or engaging in certain other skullduggery that Apple frowns upon. (You did? STEP BACK FROM THE EDGE!!!)

Option A: Full Enterprise

Option B: You Have No Chance To Survive Collect Your UDIDs

Option C: Public

You cannot use an Appexchange listing to host an IPA file. You need generic file storage (I've used S3) and an installation page your users can access on their devices.

Edit the second: There is one additional overwhelming advantage that is unique to Option C: all of your users receive updates simultaneously and can update without waiting on their admin to distribute your IPA to them... unless, of course, you are hosting the IPA file yourself and built your own app updating and notification mechanisms. (You did? STEP BACK FROM THE EDGE!!!)

A: Full Enterprise

B: You Have No Chance To Survive Collect Your UDIDs

C: Public

You cannot use an Appexchange listing to host an IPA file. You need generic file storage (I've used S3 for this) and an installation page your users can access on their devices.

Edit the second: There is one additional overwhelming advantage that is unique to Option C: all of your users receive updates simultaneously and can update without waiting on their admin to distribute your IPA to them... unless, of course, you are hosting the IPA file yourself and built your own app updating and notification mechanisms. (You did? STEP BACK FROM THE EDGE!!!)

Option C might be ruled out if you are using private APIs or engaging in certain other skullduggery that Apple frowns upon. (You did? STEP BACK FROM THE EDGE!!!)

7 added 226 characters in body
source | link

You cannot use an Appexchange listing to host an IPA file. You need generic file storage (I've used S3) and an installation page your users can access on their devices.

From your comments below, it sounds like you are headed towards Option A. It is irrelevant whether your Appexchange listing is public or private or how many listings you maintain; you will inevitably be shut down by Apple. In case it's not obvious, I think only one of the above options is worth your time. :)

LastlyEdit the second: you cannot use an Appexchange listing to host an IPA file. You need generic storage (S3There is a good fit) and an installation pageone additional overwhelming advantage that is unique to Option C: all of your users receive updates simultaneously and can accessupdate without waiting on their devicesadmin to distribute your IPA to them... unless, of course, you are hosting the IPA file yourself and built your own app updating and notification mechanisms. (You did? STEP BACK FROM THE EDGE!!!)

From your comments below, it sounds like you are headed towards Option A. It is irrelevant whether your Appexchange listing is public or private or how many listings you maintain; you will inevitably be shut down by Apple. In case it's not obvious, I think only one of the above options is worth your time. :)

Lastly: you cannot use an Appexchange listing to host an IPA file. You need generic storage (S3 is a good fit) and an installation page your users can access on their devices.

You cannot use an Appexchange listing to host an IPA file. You need generic file storage (I've used S3) and an installation page your users can access on their devices.

From your comments below, it sounds like you are headed towards Option A. It is irrelevant whether your Appexchange listing is public or private or how many listings you maintain; you will inevitably be shut down by Apple. In case it's not obvious, I think only one of the above options is worth your time. :)

Edit the second: There is one additional overwhelming advantage that is unique to Option C: all of your users receive updates simultaneously and can update without waiting on their admin to distribute your IPA to them... unless, of course, you are hosting the IPA file yourself and built your own app updating and notification mechanisms. (You did? STEP BACK FROM THE EDGE!!!)

6 edited body
source | link
5 added 30 characters in body
source | link
4 added 1922 characters in body
source | link
3 deleted 124 characters in body
source | link
2 added 184 characters in body
source | link
1
source | link