Table of contents
TL;DR
- Export your Draftbit project as a reference. Inventory navigation, requests, and any settings your app needs to run.
- Rebuild one flow in Vibecode and run it against a test environment. Test success, errors, and sign-in.
- For an existing store listing, confirm its app identifier and signing setup before you upload the new build.
To move a Draftbit app to Vibecode, use the exported project to document how your app works, then rebuild the mobile screens against the same API. Start with one complete flow and verify it against a development environment before you switch any live traffic.
Get the source and map the navigation
Use Draftbit's project export or GitHub export to save the code. Export access depends on your plan. The code gives you the screen names, controls, API calls, and navigation rules you need for the rebuild. Draftbit project export · Draftbit GitHub export
Pick the most-used flow and write it as a series of taps. In a field inventory app, it could be Assigned jobs → Job details → Record stock → Save. Note what happens after a save, where Back goes, and what the screen shows when the connection drops. Record the permissions needed for features like a camera or a file picker.
Carry over the API and authentication
List the API routes involved, the development and production addresses, and how the app attaches a user session to requests. Include example responses with test records or fictitious data. Keep private keys and production tokens out of the brief.
Write down what should happen when a session expires. For example, if an inventory edit fails because the session expired, the app should let the user sign in again and keep the unsent form available. Test the flow with a test user that has limited permissions.
Rebuild a flow in Vibecode
Pick iOS app in Vibecode for SwiftUI, or Mobile app (Legacy) under Legacy for React Native on iPhone and Android. Attach screenshots from the current app and give the agent the API details for your test environment. Vibecode mobile project types
Rebuild one Draftbit flow · 118 words
Rebuild the attached Draftbit inventory flow as an iPhone app in SwiftUI. Start with the Assigned jobs screen. Tapping a job opens its details and current stock counts. Let the user change one count and save it through the development API contract attached below. After a successful save, show the updated count and return to the same job. Keep an unsent edit on screen if the network drops. If the session expires, allow sign-in and keep the edit available. Use the test account and test records only. Verify that I can change one test count in the app and see it in the existing Draftbit app. Also test an expired session and a save that the server rejects.
Once the first flow works, add the remaining screens and compare them to the old app on a phone. Check that deep links reach the right screen and that any account, purchase, or offline behavior you rely on still works.
Update the existing store listing
For an iPhone app, check the existing bundle ID and signing setup before uploading to the same App Store Connect record. Install a TestFlight build and test with an existing test account. On Plus or higher, Vibecode can submit a Swift build using your Apple Developer account. Apple's update instructions · Vibecode TestFlight guide
For an Android update, keep the package name, verify the upload key, and increase the version code. Export the Expo project on Pro or higher and build an AAB for your Play Console release. Android APK and AAB guide
Try an original Vibecode build promptFrequently asked questions
Can I import my Draftbit project into Vibecode?
Start a new project and use the Draftbit export, screenshots, and API contract as references for the rebuild. Give the agent one navigation flow to recreate first.
Can I keep my Draftbit backend?
You can keep the same API if the new app can sign in and call the endpoints securely. Check the development and production URLs and test how the server scopes records to each user.
Can I release the Vibecode build as an update?
Check the existing listing's bundle ID or Android package name, the signing setup, and the app version. Build the replacement against that identity if you intend to update the listing.
About the editorial team
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.
More from the Vibecode blog
Tutorial
How to turn a Blink.new project into a mobile app
Rebuild a Blink.new project as a mobile app in Vibecode. Map the Blink SDK calls, connect the backend, and test the new app in TestFlight.
Tutorial
How to turn an Emergent project into a mobile app
Turn your Emergent project into a mobile app with Vibecode. Rebuild the screens, connect your existing backend, and ship to the App Store.
New to AI app building? Read what vibe coding means or compare the best AI mobile app builders. Have an idea? See if you can vibe code it.