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

# App Maker

## App Maker

App Maker is Akinon's platform for building, releasing, and operating white-label mobile commerce apps for iOS, Android, and Huawei. From a single project you can manage store credentials, trigger native builds, distribute to the App Store and Google Play, ship over-the-air (OTA) updates with CodePush, and enforce mandatory upgrades with Force Update.

### Start Here

New to App Maker? Follow the [Quickstart: From Zero to First Release](/tutorials/app-maker/getting-started/quickstart-from-zero-to-first-release.md) — it walks the full journey in order and links to the detailed guide for each step.

### How the Documentation Is Organized

The sidebar follows the product lifecycle, top to bottom:

| Section                     | What you will find                                                                                     |
| --------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Getting Started**         | The end-to-end Quickstart journey.                                                                     |
| **Team & Access**           | Organization users, roles and privileges, invitations.                                                 |
| **Projects**                | Creating a project and configuring it: credentials, environment variables, webhooks.                   |
| **Create App on Stores**    | Prerequisite store records on App Store Connect and Google Play Console.                               |
| **Build & Distribute**      | The end-to-end build guide (Deploy Project), build details, and distributing builds to the app stores. |
| **Operate & Update**        | Post-release operations: CodePush OTA updates, Force Update, release tracking.                         |
| **Developer Tools & CLI**   | SSH keys, access tokens, local project setup, plugin development, dependency management.               |
| **Account & Notifications** | Personal profile, language, and notification preferences.                                              |

### The Typical Journey

1. **Set up the team** — invite users and assign [roles](/tutorials/app-maker/team-and-access/users-and-roles.md).
2. **Create a project** — see [Create Project](/tutorials/app-maker/projects/create-project.md).
3. **Add credentials** — certificates, keystores, and store API keys under [Credentials](/tutorials/app-maker/projects/settings/credentials.md).
4. **Create the app records on the stores** — see [Create App on Stores](/tutorials/app-maker/create-app-on-stores.md).
5. **Build** — trigger a build following Deploy Project and inspect it in [Build Detail](/tutorials/app-maker/build-and-distribute/build-detail.md).
6. **Distribute** — send the build to TestFlight / Play tracks via [Distribute to Stores](/tutorials/app-maker/build-and-distribute/distribute-to-stores.md).
7. **Operate** — ship OTA fixes with [CodePush](/tutorials/app-maker/operate-and-update/codepush.md) and enforce upgrades with [Force Update](/tutorials/app-maker/operate-and-update/force-update.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akinon.com/tutorials/app-maker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.