Mobile apps (iOS and Android)
ESTAGE includes an AI mobile app builder. Describe the app you want and Genesis builds a real React Native (Expo) application for iOS and Android — not a web page in a shell, not a progressive web app. It is the same chat, the same live preview, and the same visual editing you use for a website, pointed at a different target.
Starting an app
Section titled “Starting an app”Two ways in:
- A new app — start a new project and choose the mobile target on the dashboard.
- An app next to an existing site — add a Mobile app to a project you already have. One project can hold a Website, a Web app, and a Mobile app side by side; each keeps its own chat, its own files, and its own preview, while sharing the project’s team and domain.
The mobile builder is available to eligible accounts. If you don’t see the option, it hasn’t been enabled for your account yet.
Seeing it on your phone
Section titled “Seeing it on your phone”Apps preview through Expo Go, the free Expo client from the App Store or Google Play. The builder shows two QR codes:
- Live preview — points at your running build. Scan it and every change you ask for appears on the phone as you work.
- Shareable QR — a published snapshot of the app. It keeps working after you close the builder, so you can send it to a client or a tester and they can open the app whenever they like. Publish again to update what they see.
Both need Expo Go installed on the phone. This is a preview tier, not a store install.
Publishing to the stores
Section titled “Publishing to the stores”The publish wizard builds a real, signed binary and submits it:
- iOS — the App Store, including TestFlight for testers.
- Android — Google Play.
You bring your own Apple Developer and Google Play accounts and their credentials — the app is published under your developer identity, because the app belongs to you. The wizard walks through the credentials it needs and keeps them for later builds.
What the app can use on the device
Section titled “What the app can use on the device”Mobile projects are native, so they reach the phone’s own hardware and system views. The AI picks versions of these libraries that are compatible with your app’s Expo build, so you ask for the feature rather than for a package:
| Ask for | What lands in the app |
|---|---|
| ”let people take a photo” | The device camera |
| ”let them pick an image from their phone” | The system photo picker / gallery |
| ”play this video in the app” | Native video playback |
| ”use these icons / this logo” | SVG graphics rendered natively |
| ”show our help center inside the app” | An embedded web view |
What’s different from the website target
Section titled “What’s different from the website target”The app is native, so the web-shaped pieces of the platform don’t apply to it — order forms, the tracking pixels, and one-click localization are website features. What stays the same is the way you work: describe changes in chat, watch them appear, revert a turn you didn’t like, and open the code when you want to.