Non-profits and dev program requirements
Non-profits and dev program requirements
- Subject: Non-profits and dev program requirements
- From: Fritz Anderson <email@hidden>
- Date: Mon, 24 Sep 2012 13:12:15 -0500
[I'm taking this to a new thread. It's a response to a posting in the thread "Re: Apple app review guideline.. really not clear." I'm open to the suggestion that it is off-topic for this list.]
The focus of Apple's iOS enterprise developer program is to balance two needs:
• Apple needs to curate iOS applications that may fall into the hands of the general public. Period. Not negotiable.
• Companies (usual example) need apps that can work with their expense-reporting systems without the security concerns of sending their expense-reporting client software to the whole world.
The Enterprise Developer Program is a compromise. It allows well-defined and -identified organizations to bypass the App Store to distribute an app ON THE STRICT CONDITION that the app never be available outside the organization. It is designed not to be an alternative to the App Store. There is an exception for including consulting developers, but the central point is that the app can't fall into the hands of anyone the organization can't fire. (I paraphrase; the agreement instead defines persons who qualify as being in-organization.)
It therefore doesn't matter if the organization is non-profit or otherwise nice. Profitability and distribution are separate issues. Life lesson: Non-profitability excuses you from almost nothing in this world.
Related is the regular, App Store developer program, which by default is for solo developers. Organizations (I believe they need to have DUNS numbers) can employ multiple developers. I don't have the agreement in front of me, but I'm pretty sure that it extends to members of the organization who have been registered; or to project-specific consultants (who have been registered). Again, nobody the organization can't fire.
My employer is a non-profit. It has enterprise and app-store program memberships. They're the same as for any other entity.
Independent iOS developer-program members could contribute to an open-source code base, which a hub organization could submit on its own to the App Store. (I don't have the agreement in front of me, and there is probably some circumstance that Apple could find abusive. I'd be glad to hear more on this.)
Apple doesn't care what you do for a back-end for your application, so long as it doesn't somehow abuse the users of your application. It doesn't care what you put in your Mac software, so long as it isn't sold on the Mac App Store or signed for Gatekeeper.
I don't know anything about the B2B store, but my guesses (for iOS) would start at the same restrictions as for the ordinary iOS developer programs.
— F
On 24 Sep 2012, at 11:57 AM, Daniel Beatty <email@hidden> wrote:
> I do have a question on this same heading. If a existing enterprise developer is wanting to s/he wants help a non-profit organization get a developer setup so that multiple iOS and Mac developers can contribute to that organizations success, how would they do it? Namely, the idea is for the organization's servers, cloud, and apps to be something of the organization as opposed to any one developer.
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden