> 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/apple-developer-vs-app-store-connect.md).

# Apple Developer vs App Store Connect

### What is the difference between an Apple Developer account and an Apple App Store account?

The Apple Developer account and the Apple App Store account serve different purposes but are both required for publishing and managing iOS apps.

* **Apple Developer account**
  * Required to build, sign, and publish apps on the App Store.
  * Grants access to developer tools, certificates, and app distribution features.
  * Must be active with an annual subscription.
* **Apple App Store account (App Store Connect)**
  * Used to manage apps after they are published.
  * Allows you to upload builds, configure app metadata, set pricing, and monitor app performance.
  * Linked to your Apple Developer account for publishing.

{% hint style="success" %}
Subscribing to the [**Apple Developer Program**](https://docs.appmysite.com/app/download/ios/create-apple-developer-account.md) gives you access to both the Developer account and App Store Connect under the same membership.
{% endhint %}


---

# 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/apple-developer-vs-app-store-connect.md?ask=<question>&goal=<user_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.
