> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/publishing-and-distribution/choosing-apple-developer-program.md). # Choosing Apple developer program ### Which developer program should you choose on Apple? Apple offers two types of memberships for its Developer Program: * **Individual** – Best for solo developers who plan to manage their app independently without additional team members. * **Organization** – Ideal for businesses and teams that need to collaborate. This option allows you to invite team members or third-party services like AppMySite to assist with app management. If you plan to manage your app on your own and don’t require assistance from anyone else, choose the Individual membership. If you plan to invite your team members or AppMySite to your developer account, choose the organization membership. To create a developer account as an organization, you’ll be required to enter a D-U-N-S Number registered to your company. Read more about the comparison between developer programs on the [official Apple website](https://developer.apple.com/support/compare-memberships/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.appmysite.com/frequently-asked-questions/publishing-and-distribution/choosing-apple-developer-program.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.