Building Mobile Apps
A Complete Guide to the Mobile App Agent
From a single prompt to production-grade native iOS and Android apps — no setup, no local tooling. Previewed on your phone in minutes and publishable to the App Store and Google Play.
Overview​
Abacus AI Agent can build complete, production-grade mobile applications from natural-language prompts. You describe the app you want; the agent plans the architecture, writes the frontend and a backend, runs it, and packages it into installable apps for iOS and Android.
No set-up needed. You can refine the app entirely through natural-language prompting.
What you can build​
- Cross-platform apps that run on iOS, Android, and the web from a single codebase.
- Frontend-only apps (calculators, trackers, utilities that store data on the device).
- Full-stack apps with their own backend and database (accounts, shared data, sync, leaderboards).
- Mobile app connected to an existing Abacus AI web app that reuses its backend and data.
- Native iOS apps written in Swift + SwiftUI for iPhone only apps
See it in Action​
1. Interactive Storefront
2. Gamified Skill Builder
3. AI Running Coach
4. GPS Survival Game
Quick Start​
Building your first app takes three steps.
- Describe the app. In the chat, tell Abacus AI Agent what you want — for example, "Build a habit-tracking app with daily streaks and reminders." The agent plans the architecture and builds it.
- Preview it. Open the App pane (the "App" button on the right rail of the chat), then the Preview tab to see the app running live in an embedded web view. To try it on a real phone, build and install it via the Deploy button.
- Build & publish. When you are happy, use the Deploy button (top-right of the App pane) to build an installable package, and the guided publishing flow to submit to the App Store or Google Play.
You do not have to get everything right in the first prompt. Build a first version, preview it, then ask for changes in plain language — the agent iterates on the same app
Preview & Testing​
Every app can be previewed instantly from the right pane of the agent conversation.
Cross-platform apps (React Native) — browser preview​
- Preview tab (App pane): the app runs live in an embedded browser web view (Expo Web) — instant, with no phone or install needed.
- The web preview validates the web version. Layout, most screens, and logic can be checked here.
- Platform-specific rendering, gestures, and push notifications, camera, etc. may behave differently — or not at all — in the web preview.
- Always test native features on a real device using an installed build (Android APK/AAB, or an iOS/TestFlight build).
For Native iOS (Swift) apps — live simulator preview​
- Native iOS apps preview as a live, interactive iOS simulator streamed into the Preview tab — tap, type, and scroll through the real app.
- Press "Start live preview." to start testing
Building Installable Packages​
When your app is ready, package it into installable files from the Deploy button at the top-right pane.
| Build type | Platform | Use |
|---|---|---|
| APK | Android | Install directly on a device for testing. |
| AAB | Android | Upload to Google Play (required format for the store). |
| IPA / TestFlight | iOS | Install via TestFlight for testing, then submit to the App Store. |
How to build​
- Android: Deploy → Build Mobile App → choose APK or AAB.
- iOS: Deploy → Publish to App Store (builds an IPA and uploads it to TestFlight).
- For iPhone-only Apps - Native iOS (Swift): Deploy → build to TestFlight — there is no APK/AAB and no Android build.
- For full-stack apps, the backend must be deployed first — use Deploy → Deploy Backend (the agent usually does this for you at checkpoint).
Timing & status​
- Packaging typically takes 10–15 minutes — longer for large apps with many dependencies.
- Build status and artifact download links appear on the build-type pills at the top-right of the App pane.
Building for iOS requires your own Apple Developer credentials and membership in the Apple Developer Program. Android builds have no such prerequisite.
Publishing to the Apple App Store​
After an iOS build reaches TestFlight, a "Publish to the App Store" section appears in the Deploy panel with two options.
This App Store flow applies to both cross-platform and native iOS (Swift) apps.
| Option | What happens |
|---|---|
| Guide me | The agent prepares your screenshots, listing text, and exact, step-by-step App Store Connect instructions. You fill in the console yourself. |
| Do it for me | The agent fills in App Store Connect for you via browser automation. You only press the final "Add for Review" button. |
What is prepared for you​
- Real screenshots captured from your running app at the exact sizes the stores require (uploaded under the iPhone and iPad 13" tabs), verified before upload.
- A reviewer demo account (if your app has a login), verified against the live backend.
- A live Privacy Policy URL and Support URL (added to your deployed backend when needed).
- All listing fields — app name, subtitle, description, keywords, category, age rating, and App Privacy data answers — drawn from what your app actually does.
Neither you nor the agent auto-submits for review. The final "Add for Review" is always yours. Common blockers: unpublished App Privacy answers, missing iPad screenshots, missing demo account.
Publishing to Google Play​
After an Android AAB build succeeds, a "Publish to the Play Store" section offers the same "Guide me" and "Do it for me" options for the Google Play Console.
Native iOS (Swift) apps cannot publish to Google Play — they are iPhone-only. For an Android release, build a cross-platform app.
What is prepared for you​
- Real phone screenshots at valid sizes, plus a 512×512 app icon and a 1024×500 feature graphic (both required by Google).
- A live Privacy Policy URL and a reviewer demo account where needed.
- All listing fields and declarations — title, descriptions, category, content rating, target audience, and Data safety answers.
Organisational accounts can create a Production release and submit for review directly. New personal accounts must first run a Closed test with at least 12 testers for 14 days before Production unlocks. The .aab first uploads as a draft on the Internal testing track, which does not satisfy that requirement.
Your app's package name is set in the App identifiers row of the Deploy panel (directly above the Build button); it validates the value and refuses one already held by another app or a published app. As with Apple, the final publish/review button is always yours.
Troubleshooting & FAQ​
Q: I can't find the Preview or Deploy button.
A: They live inside the App pane, not the chat view. Click the "App" button on the right rail of the chat to open it; Preview is a tab and Deploy is at the top-right.
Q: The preview won't load the app.
A: The preview runs in your browser (an embedded web view). Reload the Preview tab; if it still fails, open the Logs viewer in the App pane and share the errors with the agent. To test on a phone, build and install the app.
Q: Push notifications don't work in the preview.
A: That is expected — push is native-only. Build an APK or IPA and test on a real device.
Q: My iOS build failed / asks for credentials.
A: iOS builds require an Apple Developer Program membership and your Apple ID credentials, including any 2FA prompt. Make sure your account has Developer Program access.
Q: My Play Store upload was rejected for a package-name mismatch.
A: The AAB's package name must exactly match your app's configured Android package name. Ask the agent to confirm the identifier before rebuilding.
Q: Can I change my app's package name / bundle ID after building?
A: No — identifiers lock once you build for that platform or set up push credentials, because the stores bind your app identity to them. Set the identifier before your first build.
Q: How do I get my existing device data into a new server-backed version?
A: When a backend is added to an app that previously stored data on-device, existing local data is left in place and keeps working. Ask the agent to copy it into the new server-backed view as a separate step if you need it there.
Q: How long does a build take?
A: Usually 10–15 minutes, longer for large apps. Watch the build pills at the top-right of the App pane for status and download links.
Q: Can I build a native iPhone (Swift) app, and how do I choose the app type?
A: Yes. By default the agent builds cross-platform React Native apps (iOS, Android, and web). Ask for a "native iOS" or "Swift" app to get a fully native SwiftUI iPhone app. Native iOS apps are iPhone-only and require a paid plan.
Q: Does a native iOS (Swift) app also run on Android?
A: No — native iOS apps are iPhone-only. For Android, use a cross-platform app.
Still Need Help?​
If you're still stuck, contact support — we're here for you.