Building mobile apps
Select Mobile in the platform toggle, describe what you want, and get a native iOS and Android app from a single codebase.
Getting started
Try a prompt like this:
"Build a fitness tracker with:
- Daily workout logging
- Exercise library with categories
- Progress charts
- Profile with stats
- Clean dark theme"
Previewing on your phone
After code generates, open the preview with one of these options:
- iOS: Download the Appifex app (App Store), then scan the QR code in the app.
- Android: Open the preview URL in your phone browser from the QR code page.
- Desktop/browser: Open the same preview URL directly in your browser.
You can share the QR code page with anyone — no login required.
Navigation
Request specific patterns by describing what you want:
"Use bottom tab navigation with Home, Search, and Profile tabs"
Native features
Request device capabilities directly in your prompt:
| Feature | Example prompt |
|---|---|
| Camera | "Add camera access to scan barcodes" |
| Location | "Include GPS for location tracking" |
| Notifications | "Add push notifications for reminders" |
| Biometrics | "Add Face ID / fingerprint login" |
In-app purchases
Connect RevenueCat for subscriptions:
"Add monthly subscription via RevenueCat with a paywall for premium features"
Adding mobile to existing projects
Already have a web app? Add a mobile version:
"Create a mobile app that connects to the existing backend.
Use the same authentication and data."
Appifex reads your existing backend and builds mobile screens connected to the same APIs.
Publishing to app stores
Submit builds directly to TestFlight and Google Play from Settings.
iOS:
- Connect your Apple Developer account (guided wizard)
- Go to Settings → Publishing → Submit to store
- Click Submit — your app builds and uploads to App Store Connect
Android:
- Connect your Google Play account (guided wizard)
- Go to Settings → Publishing → Submit to store
- Click Submit — your app builds and uploads to Play Console
After your initial submission, over-the-air updates can ship JavaScript/TypeScript bundle changes without a new store review.
- OTA-eligible: UI changes, app logic, static assets, and JS-only configuration/feature-flag updates.
- Requires new store submission and review: native code changes, native module or SDK additions/upgrades, and manifest/entitlement/permission changes.
Example prompts
Social app:
"Photo feed with likes and comments, user profiles with follow,
direct messaging, push notifications"
E-commerce:
"Product catalog with categories, search and filters,
shopping cart, checkout flow"
Productivity:
"Note-taking with rich text editor, folders and tags,
search across all notes, sync across devices"