> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/motors-app-documentation/ios-app-build/app-store-connect.md).

# Step 1 – App Registration on App Store Connect

## Prerequisites and environments

This manual provides a step-by-step demonstration of releasing a Motors app to the [App Store](https://developer.apple.com/app-store/submissions/) and [TestFlight](https://developer.apple.com/testflight/) .

You need to enroll in the **Apple Developer Program** in order to publish your app to the App Store. You can read more about developer program and its options [here](https://developer.apple.com/programs/).

App Store Connect is a web-based tools kit for controlling apps sold on the App Store. As a member of the Apple Developer Program, you will set up your app name, description, screenshots, submit and manage apps, invite users to test with TestFlight, monitor sales reports, and more.

Tip: You can review the [App Store Connect](https://developer.apple.com/videos/play/app-store-connect/105/) tutorial for a more detailed overview.


---

# 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.stylemixthemes.com/motors-app-documentation/ios-app-build/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.