4 ms·

That's $99/year and Apple really doesn't see this as a way to install programs that aren't on AppStore. It's really just meant to compile locally, deploy local

That's $99/year and Apple really doesn't see this as a way to install programs that aren't on AppStore. It's really just meant to compile locally, deploy locally to your devices or submit to AppStore. Even the number of devices you can support per year in your profiles is limited to 100, probably because they don't want you to use it as a distribution mechanism, just a temporary testing mechanism. 100 devices per year is actually rather limited if you do custom work and each client comes with his own list of 5-20 devices they want to test onto.

masklinn 16y ago
> Even the number of devices you can support per year in your profiles is limited to 100, probably because they don't want you to use it as a distribution mechanism Really? Even though they call it a distribution mechanism themselves[0]? Interesting. > 100 devices per year is actually rather limited if you do custom work and each client comes with his own list of 5-20 devices they want to test onto. If you do custom work for clients, then clients are supposed to get their in-house license for distribution. Either a company developer program, or an Enterprise program[1] which exists very specifically for company in-house deployments. Using your personal developer key for client-site deployment is not a good idea and makes low to no sense. Are you really suggesting that you should manage and deploy your client's device park forever? [0] http://developer.apple.com/programs/ios/distribute.html http://developer.apple.com/programs/ios/distribute.html [1] http://developer.apple.com/programs/ios/enterprise/ http://developer.apple.com/programs/ios/enterprise/
- fierarul 16y ago
  >Really? Even though they call it a distribution mechanism themselves[0]? Interesting. It's not a mass distribution mechanism where, for example, you could just add the UDIDs of all your users. Of course it's a distribution mechanism, but it's just meant for testing, not a competition to AppStore. That's what I was talking about. >If you do custom work for clients, then clients are supposed to get their in-house license for distribution. Really? And what do you do when the customer wants you to start work NOW and they'll apply to Apple in the mean-time for their own keys ? Do you just tell them you can't email them a simple prototype because, well, you're too lazy to add some device IDs to your own list ? Anyhow, your reply seems to be quite orthogonal to what I meant and those links and your tone are mildly insulting. My point was that the developer account isn't really designed as a way to install your own apps for the masses (hence my examples).
  - masklinn 16y ago
    > It's not a mass distribution mechanism where, for example, you could just add the UDIDs of all your users. not it's not a mass distribution mechanism. But it's still a distribution mechanism, and one that is supported. > but it's just meant for testing That's woefully incorrect. It can be used for testing, but it definitely isn't just meant for that. > Really? And what do you do when the customer wants you to start work NOW and they'll apply to Apple in the mean-time for their own keys ? Do you just tell them you can't email them a simple prototype because, well, you're too lazy to add some device IDs to your own list ? No but that's a very different issue. You don't need to enable 5000 devices to test the application, and you will reclaim those spots later on. > those links and your tone are mildly insulting. Feel free to blame yourself. > My point was that the developer account isn't really designed as a way to install your own apps for the masses. Then you might have wanted to write that. And you'd have gotten a "No, really?" instead. > (hence my examples) You only gave one example and it had no relation to mass-distribution. Quite the opposite, in fact.

masklinn 16y ago

> Even the number of devices you can support per year in your profiles is limited to 100, probably because they don't want you to use it as a distribution mechanism Really? Even though they call it a distribution mechanism themselves[0]? Interesting. > 100 devices per year is actually rather limited if you do custom work and each client comes with his own list of 5-20 devices they want to test onto. If you do custom work for clients, then clients are supposed to get their in-house license for distribution. Either a company developer program, or an Enterprise program[1] which exists very specifically for company in-house deployments. Using your personal developer key for client-site deployment is not a good idea and makes low to no sense. Are you really suggesting that you should manage and deploy your client's device park forever? [0] http://developer.apple.com/programs/ios/distribute.html http://developer.apple.com/programs/ios/distribute.html [1] http://developer.apple.com/programs/ios/enterprise/ http://developer.apple.com/programs/ios/enterprise/

fierarul 16y ago
>Really? Even though they call it a distribution mechanism themselves[0]? Interesting. It's not a mass distribution mechanism where, for example, you could just add the UDIDs of all your users. Of course it's a distribution mechanism, but it's just meant for testing, not a competition to AppStore. That's what I was talking about. >If you do custom work for clients, then clients are supposed to get their in-house license for distribution. Really? And what do you do when the customer wants you to start work NOW and they'll apply to Apple in the mean-time for their own keys ? Do you just tell them you can't email them a simple prototype because, well, you're too lazy to add some device IDs to your own list ? Anyhow, your reply seems to be quite orthogonal to what I meant and those links and your tone are mildly insulting. My point was that the developer account isn't really designed as a way to install your own apps for the masses (hence my examples).
- masklinn 16y ago
  > It's not a mass distribution mechanism where, for example, you could just add the UDIDs of all your users. not it's not a mass distribution mechanism. But it's still a distribution mechanism, and one that is supported. > but it's just meant for testing That's woefully incorrect. It can be used for testing, but it definitely isn't just meant for that. > Really? And what do you do when the customer wants you to start work NOW and they'll apply to Apple in the mean-time for their own keys ? Do you just tell them you can't email them a simple prototype because, well, you're too lazy to add some device IDs to your own list ? No but that's a very different issue. You don't need to enable 5000 devices to test the application, and you will reclaim those spots later on. > those links and your tone are mildly insulting. Feel free to blame yourself. > My point was that the developer account isn't really designed as a way to install your own apps for the masses. Then you might have wanted to write that. And you'd have gotten a "No, really?" instead. > (hence my examples) You only gave one example and it had no relation to mass-distribution. Quite the opposite, in fact.