> ## Documentation Index > Fetch the complete documentation index at: https://docs.mythex.ai/llms.txt > Use this file to discover all available pages before exploring further. # Mobile apps > Turn your Mythex web app into an Android and iPhone app from the chat — built on Mythex's build machines, sent to Google Play internal testing and TestFlight, on the Pro plan. # Mobile apps Mythex can turn the app you built into a phone app for **Android** and **iPhone**. It stays one project: the agent wraps your web app with [Capacitor](https://capacitorjs.com) (always its latest version), and your website keeps working exactly as before. > [!NOTE] > > Mobile apps are part of the **Pro** plan and up (Business, Enterprise). On Free, the agent can't build, connect a store account, or read your store listings. See [Plans](https://docs.mythex.ai/billing/plans.md). ## Start a build Three ways, all of which end up in the chat: * **Publish → Android or iPhone.** The Publish button has tabs: **Website**, **Android** and **iPhone**. A phone tab shows where that app stands and which store account it uses, and its button (**Build Android app**, **Build iPhone app** or **Build new version**) sends the request to the chat for you. * **`/mobile`** in the message box, followed by what you want: *"/mobile Android, and send it to Google Play"*. * **Your own words:** *"Make this an Android app and put it on Google Play."*, *"Build the iPhone app."* ![Publish → Android: the app's latest build, its Google Play account, and Build new version](https://mintcdn.com/mythex/CIs3OEtRfkVYDlLf/images/mobile-publish-android.png?fit=max\&auto=format\&n=CIs3OEtRfkVYDlLf\&q=85\&s=f7247ce930b40abe1d0baffcb49afe3b) Each request builds only the platform you asked for. The agent sets the project up for phones the first time (you don't need to answer anything technical), then builds on Mythex's build machines — there is no Xcode or Android Studio to install. A card in the chat follows each build: | Card | What it means | | - | - | | **Preparing → Building … → Step 3 of 3** | The build machine's real steps, with how long it usually takes. | | **Ready to upload** · Download | Android, no Google Play account connected: the file is ready. | | **In internal testing** · Play Console | Android, sent to your app's internal testing track in Google Play. | | **In TestFlight** · TestFlight | iPhone, uploaded to your TestFlight. | | A grey line under the status | A step on your side (create the app in the store, give access). The card says exactly what. | | A red line | Something in the app's code stopped the build — the agent reads the build output and fixes it. | ![An Android build that went to Google Play: In internal testing, with a Play Console button](https://mintcdn.com/mythex/CIs3OEtRfkVYDlLf/images/mobile-card-play.png?fit=max\&auto=format\&n=CIs3OEtRfkVYDlLf\&q=85\&s=8d8b2a04b1830d1189684abd0e8a0fe8) The card only shows where the build stands. To fix or rebuild, ask the agent. ## Store accounts | Store | What you connect | Without it | | - | - | - | | Google Play | Your own Google service account key (a JSON file) — [Android & Google Play](https://docs.mythex.ai/mobile/android-google-play.md) | Android builds are a file you download and upload yourself | | App Store | An App Store Connect API key (a .p8 file) — [iPhone & App Store](https://docs.mythex.ai/mobile/iphone-app-store.md) | iPhone builds can't be made: Apple requires signing | When the agent needs an account, it pauses and shows a **Connect** panel above the message box (like [secrets in chat](https://docs.mythex.ai/features/secrets-in-chat.md)); the key is checked with the store before it's saved. Keys are stored encrypted, per project, and are never shown again. Only the project's **owner** can connect or disconnect them; a teammate's build uses the owner's account. ![Project settings → Mobile app: the Android file, and the Google Play and App Store accounts](https://mintcdn.com/mythex/CIs3OEtRfkVYDlLf/images/mobile-settings.png?fit=max\&auto=format\&n=CIs3OEtRfkVYDlLf\&q=85\&s=b4bea6aaf87b50d4450b21838cad1bfc) Manage them any time in **Project settings → Mobile app**, which also has the latest Android file to download. A key you connected to another of your projects can be reused there with one click. ## What the agent can do in the stores With an account connected, the agent can read and change your store presence for you — the listing text and screenshots, testing tracks, versions and build numbers, testers, and release status: * *"What version is on Google Play and TestFlight right now?"* * *"Write the store description and add screenshots."* * *"Move the latest build to production."* It only ever touches this project's app. Anything the public sees or that can't be taken back — releasing to production, open testing, rollouts, prices, submitting for review, deleting — it asks you first. A few things are only on the stores' websites: creating the app the first time, Google Play's **Data safety** form and **content rating**, and Apple's **App Privacy**. The agent tells you when you need one. ## Cost A build is paid in **Build credits**: what the build machine actually costs, at the usual credit rate. An Android build is usually under **1 credit**; an iPhone build (on a Mac) a few credits. A build that stops on Mythex's side isn't charged. The agent's store calls cost nothing beyond the chat. See [Credits](https://docs.mythex.ai/billing/credits.md). ## If your plan changes If the project owner moves to Free, builds and store calls stop, and the card says **Needs the Pro plan**. Connected store accounts stay saved (the owner can still disconnect them), and the last Android file can still be downloaded. Back on Pro, everything works again without reconnecting. ## Related * [Android & Google Play](https://docs.mythex.ai/mobile/android-google-play.md) * [iPhone & App Store](https://docs.mythex.ai/mobile/iphone-app-store.md) * [Project settings](https://docs.mythex.ai/features/project-settings.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.