We are developing an app specifically to a single customer's requirements and want to put it in the hands of their evaluation team (3 people) as we go along. Before we release the product, we'll be going with enterprise distro but we need to figure out this interim step.
-
3This is called Adhoc distribution. There are plenty of Apple docs on how to do this. – rmaddy Feb 13 '13 at 00:26
-
Thanks. The sources I've read said that Adhoc distro was not permissible to folks outside the organization, thus the question. We already have an enterprise account and the terms for that were very clear that we can only use this for internal folks. I've been looking for something on Apple's site that says an evaluation deployment for a customer review counts as "internal" but nothing I've seen supports this. – Brian Bragg Feb 13 '13 at 01:10
-
You didn't mention you were using an Enterprise account. Adhoc is normally used for testing. At least with non-Enterprice, you can use testers from anywhere. I don't know the rules of the Enterprise program. – rmaddy Feb 13 '13 at 01:15
3 Answers
Get an iOS developer account for $99 and register the devices of those three people to your account.

- 1,183
- 1
- 10
- 12
-
1We already have an enterprise account but neither enterprise nor developer accts allow for external distro. – Brian Bragg Feb 13 '13 at 01:11
I use a company called testflight, they are at testflightapp.com They make it pretty easy to distribute an application to testers when you have an ios developer account.

- 9,539
- 6
- 40
- 47
-
1We use TestFlight already for internal QA distribution but I don't believe that gets around Apple's prohibition of external distribution. I'm trying to conform to the letter of our agreement. – Brian Bragg Feb 13 '13 at 01:13
At my company, we have the customer sign up for the $99 developer program and manage their own devices, then have them add our developers as developers (surprise), and make special builds for their devices.*
We also recently had a (larger) client sign up for an enterprise account so they could distribute our builds to their employees for testing w/o having to manage UDIDs.
Takes the ball out of your court, but it does seem to adhere to the Apple standards.
*: We frequently end up releasing these custom builds to the app store via the customer's developer account, which (IIRC) is also in line with Apple standards. If the app is branded by/exclusively for a given company, it makes sense.

- 13,251
- 7
- 69
- 80