How to turn an Emergent project into a mobile app

This guide follows Vibecode's documented rebuild and publishing workflow. The handoff steps use Emergent's code and data export docs.

Vishal Dubey

Vishal DubeyReviewed by Ansh Nanda

Updated

Table of contents
  1. What to bring from your Emergent project
  2. How to rebuild an Emergent app in Vibecode
  3. Checklist before you submit
  4. Frequently asked questions

TL;DR

  • Bring screenshots, the published API URL and a list of the actions the mobile app needs to support.
  • Build a native Swift iPhone app in Vibecode, or choose React Native for iPhone and Android.
  • Reuse the backend if the mobile app can reach the API and sign in. Verify a test change shows up in both apps before you ship.
  • On Plus, Vibecode builds, signs and submits Swift apps to Apple using your developer account.

Turn your Emergent project into an iPhone app by rebuilding its screens in Vibecode and connecting them to your existing API. Start with one flow people use on their phones, such as opening a work order and marking it complete. Once that change shows up in both apps, you have a working connection to build on.

Build your mobile app in Vibecode

What to bring from your Emergent project

Gather three things before you start.

  • Screenshots. Capture the home screen and each step of the main flow at phone size. Include any important empty and error states.
  • The published API address. Use the API your current app calls so the new app can work with the same records.
  • A test account and API details. List how users sign in, which endpoints the app calls, and what each action sends. Use test data and keep private keys on the server.

Choose an iOS app in Vibecode for SwiftUI and built-in App Store submission. Choose Mobile app (Legacy) for a React Native app targeting iPhone and Android. Vibecode's Swift and React Native guide

How to rebuild an Emergent app in Vibecode

Step 1: keep your Emergent backend live

Keep the backend deployed and use the published address, such as your-app-name.emergent.host. Preview environments sleep after inactivity and can use separate data. Emergent's publishing guide

Checkpoint: open your published Emergent address in a browser. You should see your live app, not a sleeping preview.

Step 2: back up your code and data

Do this before you change anything. Emergent's export guide splits a full backup into parts:

  • Code: click + in the message box, then Save to GitHub. It needs Emergent's Standard plan or higher. On Free, you can only view and copy files from the Code button.
  • Data: Emergent's docs say your live data is in MongoDB. Download each collection from the Database Manager (Manage → Database), or email Emergent's support for a full export.
  • Secrets: copy your API keys from Manage → Secrets into a password manager. Emergent never includes them in a code export.
  • Uploaded files: ask Emergent's support. Collection downloads don't include them.

Checkpoint: you have a copy of the latest source and data, and your secrets are stored securely.

Step 3: ask Emergent's agent to describe the app

Give Vibecode the API and sign-in details it needs to connect the new screens. Send this in your Emergent project's chat.

Send this in Emergent's chat · 124 words

I'm building a mobile app that will use this project's published backend. Don't change any code. In plain words, write a handoff for the mobile developer:

1. The published backend base URL.
2. Every API route the frontend calls: method, path, what it sends and what it returns, with one example of each.
3. How sign-in works: which providers, which route starts it, what token comes back and how later requests send it.
4. Any data fields or status values the mobile screens depend on.
5. Every screen in the app, what it shows and what each button does.
6. Any third-party services (payments, email, maps, AI) and whether they're called from the frontend or the backend.

Don't include any secret keys or passwords.

Checkpoint: make one read-only request against the published API with a test account. For a field-service app, fetch a test technician's assigned jobs and confirm the response matches the web app. Keep production tokens and customer records out of the prompt.

Step 4: take screenshots of every screen

Open your published app at phone size. In Chrome, that's View → Developer → Developer Tools, then the device toolbar. Take a screenshot of each main screen, plus any empty states and error messages that matter.

If you have an Emergent mobile app, take the screenshots on your phone in Expo Go instead.

Step 5: start the right Vibecode project

In Vibecode, start a new project:

  • iOS app for a native Swift iPhone app. Vibecode can submit these to the App Store for you.
  • Mobile app (Legacy), under Legacy, for a React Native and Expo app for iPhone and Android.

Then send this prompt with your screenshots attached and Emergent's handoff pasted at the bottom. Replace the parts in square brackets first.

Reusable migration prompt for Vibecode · 190 words

Rebuild my Emergent app as a mobile app. It's [one sentence about what the app does and who uses it].

Keep the same backend. The app should call my published Emergent backend at [your published address], so it shows the same users and data as my web app. Don't create a new database.

Screens (I've attached a screenshot of each):
1. [Screen name]: [what it shows, and what each button does]
2. [Screen name]: [...]
3. [Screen name]: [...]

Navigation: [bottom tabs for X, Y and Z / a single list with a detail screen].
Sign-in: [how users sign in today, from the handoff below].

Make it feel like a real mobile app, not a website: native lists, a tab bar, pull to refresh, haptics on the main actions, and clear loading and empty states. Keep my colors and logo from the screenshots.

Before you build any screens, check one read-only route with a test account and report the response status and shape. Use placeholders for secrets. Then build the screens and test the main flows on the target platform.

Here's the backend handoff from Emergent:
[paste Emergent's answer here]

Asking the agent to call the backend first catches a wrong address or a sleeping backend before it writes any screens.

Checkpoint: the agent confirms it can read the expected response from your published API with the test account.

Step 6: test in the simulator, then against your web app

Vibecode runs your app in an iOS Simulator in your browser. Go through every screen. Then do the test that matters most:

  1. Create or change a test record, such as a work order assigned to a test technician.
  2. Open your Emergent web app and refresh.
  3. You should see the same change there.

If the change is missing, check the API base URL, environment, account and write response before you switch the app to another backend.

Sign-in needs its own check. Web logins often rely on browser redirects and cookies, and these don't always work the same way in a mobile app. Sign out, sign in with a real account, and close and reopen the app. If it breaks, paste the error into the chat. Your app can also move to Vibecode's own sign-in, which uses Better Auth. But then you'd need to move your users too.

Step 7: put it on TestFlight and the App Store

  • Swift (iOS app) projects: press Publish, then Publish to App Store. Vibecode builds, signs, uploads and submits the app for review with your Apple Developer account. Want a beta first? Ask the agent in the chat to "upload this build to TestFlight." App Store submission needs Vibecode Plus, at $20 a month.
  • React Native (Mobile app) projects: use Deploy, then Submit to App Store. Expo Launch builds the app and uploads it to App Store Connect, where you submit it for review. You'll need an Expo account. For Google Play, download your Expo project on Vibecode Pro or higher and publish it with your own Google Play Console account.

Both need Apple's Developer Program, at $99 a year. Apple's App Review page says it reviews 90% of submissions in less than 48 hours. Our guides to TestFlight and publishing to the App Store cover each screen.

If you're replacing an app that's already on the App Store, check its bundle ID and signing before the first upload. Create a new version under the existing App Store Connect record so the rebuild reaches users as an update. Apple's guide to creating a new version

Checklist before you submit

  • Your backend is published and loads at its permanent address.
  • You have a backup of your source code and data, and your secrets are stored securely.
  • Every screen works on a phone, including empty states and errors.
  • Data you change in the app shows up in your web app.
  • Sign-in, sign-out and reopening the app all work.
  • Payments work in the app. Apple's guideline 3.1.1 says digital goods and subscriptions in iOS apps generally use in-app purchase.
  • You have a privacy policy URL, and you've filled in App Privacy in App Store Connect.
  • If your app has sign-in, you have a demo account for Apple's reviewers.
  • For Android: Google requires a closed test with at least 12 testers opted in continuously for 14 days before requesting production access on personal developer accounts created after November 13, 2023. Google Play testing requirements

Our App Store review checklist covers the most common rejection reasons.

Build your mobile app in Vibecode. Your first build is free

Frequently asked questions

Can I import my Emergent project into Vibecode?

Start a new project in Vibecode and give the agent screenshots, a description of each screen and the API details. The agent uses those to rebuild your screens and connect to your existing backend.

Can I keep my Emergent users and data?

Yes, if the new app can use the existing API and sign in with the same backend. Test with an existing account and check that a test change appears in both apps. To move hosting as well, export and migrate the database, file storage and authentication separately.

Should I build the mobile version in Swift or React Native?

Choose the iOS app project in Vibecode for an iPhone app built in SwiftUI. Choose Mobile app (Legacy) to build one React Native project for iPhone and Android.

Do I need a Mac to publish with Vibecode?

Vibecode runs the iOS Simulator in your browser and builds Swift apps on cloud Macs. On Plus, it signs and submits your app with your Apple Developer account.

Can I publish a Vibecode rebuild as an update to my existing app?

For an existing App Store listing, use the same bundle ID and App Store Connect record. Check the app's identity and signing before you upload your next release.

How do I get the Android version on Google Play?

Build a React Native app in Vibecode, download the Expo project on Pro or higher, and publish it with your own Google Play Console account.

About the editorial team

Vishal Dubey

Product Engineer at Vibecode

Vishal is a product engineer at Vibecode. Before Vibecode he did product engineering at EarnIn and co-founded Ivella (YC S21), a banking app for couples. He studied computer science at Duke.

Ansh Nanda

Co-founder and CEO of Vibecode

Ansh is the co-founder and CEO of Vibecode. Before Vibecode he was employee #7 at Bluesky and helped grow it to 3 million users. He studied computer science at Duke.

Build the first version today

Describe the app you want. Vibecode creates a working project you can preview and revise.