> 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/install-android-and-ios-app.md).

# Install Android & iOS app

### How to install your iOS and Android app?

Once your app is live on the app stores, you and your customers can easily download and install it on any supported device.

#### Installing the Android app

* Open the Google Play Store on your Android device.
* Search for your app by its name.
* Tap Install to download the app.
* Once installed, tap Open to launch it.

{% hint style="success" %}
You can also share the Play Store link directly with your users to make downloading easier.
{% endhint %}

#### Installing the iOS app

1. Open the App Store on your iPhone or iPad.
2. Search for your app by its name.
3. Tap Get and then Install to download the app.
4. Once installed, tap Open to launch it.

{% hint style="warning" %}
To install an app on an iPad, it must be published specifically for iPad. If it hasn’t been published for iPad, it cannot be installed on one.
{% endhint %}

#### For testing or private apps

If your app isn’t live on the store and you’re testing it:

* For [**Android**](/app/preview/test-apk-on-real-device.md), use the AAB or APK file to install manually.
* For [**iOS**](/app/preview/test-ipa-on-real-device.md), use TestFlight if you’re distributing your app for testing.


---

# 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/install-android-and-ios-app.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.