> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/technical/bolt-on-setup/custom-app-hosting.md).

# Custom App Hosting

Decide whether Reach or your team owns front-end hosting, releases, and app stores.

Set up Apple and Google app-store access so Reach can build and publish your branded app.

### Overview

This page covers the **minimum permissions** Reach needs to:

* create the store listing
* upload builds
* publish new versions

{% hint style="info" %}
Keep access scoped to **only the new app**. Avoid granting tenant-wide admin unless required.
{% endhint %}

### Scope

#### Included

* App Store Connect and Google Play access for the new app.
* Permissions needed to upload builds and publish releases.
* Google Play service account setup for automated uploads.

#### Not included

* Front-end hosting decisions and infrastructure setup.
* CI/CD and build pipeline design.

### Where to send invites

Invite Reach using:

* `mobile.apps@reachmobile.com`

### iOS (Apple Developer + App Store Connect)

Create a new Apple Developer account, then grant Reach access to the new app.

#### Allow Reach to build and publish

1. Create the app with a bundle identifier (example: `com.appname` or `com.appname.mobile`).
2. In App Store Connect, add `mobile.apps@reachmobile.com` as an **App Manager** for the new app.
3. Ensure the Reach user has access to **Certificates, Identifiers & Profiles** for this app.

### Android (Google Play Console)

Create a new Google Play Developer account, then grant Reach access to the new app.

#### Allow Reach to build and publish

1. Create the app with a package name (example: `com.appname` or `com.appname.mobile`).
2. Invite `mobile.apps@reachmobile.com` to the Play Console with permissions scoped to the new app.
3. Grant the minimum permissions required to upload releases and manage the store listing for that app.

#### Automate uploads (recommended)

1. In Google Play Console, go to **Setup → API access**.
2. Create a **new service account**.
3. Grant the service account access to **only the new app**.
4. Download the generated JSON key and share it with Reach.

{% hint style="warning" %}
Treat the service account JSON as a secret. Share it via an approved secure channel.
{% endhint %}

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email at <accounts@reachmobile.com> for help and support.
{% 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.reachplatform.com/technical/bolt-on-setup/custom-app-hosting.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.