a0.dev · You keep what you built
Expo screens already work in web preview and on device via the a0 app or Expo Go. Extraction means the tree, store consoles, and Convex or Supabase land under org accounts — IPA/APK paths you can rebuild, OTA within a runtime you pin, secrets outside the chat panel. We help you leave a0 Deployment as the only ship path.
30 min · senior team · leave with a clear next step
Company-level evidence
Review methodologyIn plain words
Leaving a0.dev means this: the Expo tree lives in storage you control, native builds run from a clean checkout, store credentials sit under org Apple/Play admins, and someone else can ship without opening the a0 chat. You are done when the next binary ships from that path — not from Generate & Submit on the original project.
Where people get stuck
You do not need every chat experiment. You do need the Expo tree, runtime version, deep-link schemes, backend maps, and secrets that are not stuck in the a0 panel.
Camera, push, payments, and biometrics need IPA/APK proof. Web preview never covered them.
OTA only works within the shipped runtime. Capture Expo SDK version explicitly.
Anything only in the panel is not a safe home. Fresh values on destination Convex/Supabase; rotate what touched a0.
Also try native builds, deep links, payments fail-closed, and a submit that does not need an open a0 chat.
The calm order
We do not ban prompts mid-sprint. We make owned Expo the place real releases come from — after a practiced native submit and a written way back.
01
Proven screens stay. a0 preview caches stay out. Native modules that only worked in IPA/APK need an include-or-drop pass.
02
Bundle ID and Team ID aligned. Someone else can clone and build.
03
No leftover a0 preview assumptions. Deep links list production schemes.
04
Name sample accounts and the primary journey. Time-box how long Generate & Submit-only ship is still allowed.
How to
Move Expo source, secrets, and store accounts onto an owned path. Success is a practiced native submit plus a written way back.
Step 01
Web preview, Deployment dashboard, OTA pushes, Convex/Supabase panel secrets.
Step 02
Runtime pinned. Secret names sealed. Build command written down.
Step 03
Odd roles, empty screens, native-only features.
Step 04
Compare what people see. Freeze the working tree at switch time.
Step 05
Support knows panel-era gaps. Time-box going back so two release paths do not invent accounts at once.
Read next
These pages are already on the site. Use them to pressure-test the bet before a call.
Get off a0.dev
Leave runtime dependence if the job is to stop shipping from a0 Deployment.
a0.dev to production
Own the release path if you are not ready to leave a0 yet.
Production-ready checklist
Moves, backups, and the ship list in checklist form.
Book a discovery call
Thirty minutes with a senior teammate. Honest next steps.
Verified on Clutch · 29 reviews
“What impressed us most about CodeCross was their ability to deeply understand our vision and translate it into a complete digital solution. Unlike many agencies that just focus on technical delivery, CodeCross approached our project like true partners.”
Harris Edelmam
CEO · Ombligo, Inc.
Read on Clutch“Their project management was top-notch.”
Greg Moreno Earle
Technology Executive · Driven Brands Inc.
Read on Clutch“Their eye for clean, modern design combined with technical excellence was very impressive.”
Robert Valentino
Founder · Lean Coach
Read on Clutch“We appreciated Codecross's practiced approach to development.”
Brice Wiley
Marketing Director · Lex Mundi
Read on Clutch“On the development side, everything has gone quite smoothly and perfectly.”
Brandon Patterson
Co-Owner · Cap Tech Services, LLC.
Read on Clutch“They are very thorough in their approach to the project.”
Lukas Haynes
Member Board of Directors · Protect Our Winters Action Fund
Read on ClutchInternals
Stay inside the vibe-coding cluster, or open booking and the Austin money page.
Continue
Shared intents and the rest of the a0.dev pack.
Continue
Keep prompt rhythm while Deployment ownership moves.
Continue
When tightening the public app in place is still the honest job.
Continue
Bring the Expo tree and store accounts. We will say what is missing before traffic depends on it.
Continue
Studio page if you want a partner for the move.
Before you book
Prefer writing? Send project details and we reply within one business day.
Take the Expo/RN application tree, app icon/permissions Build Settings you still need, deep-link schemes, payment product IDs, and a written map of Convex or Supabase collections. Leave preview caches, unpublished chat experiments, and collaborator personal keys out. Capture runtime version (Expo SDK) so OTA planning does not invent compatibility.
List version, Bundle ID, Team ID, and Generate & Submit steps a0 assumed. Pin Expo SDK/runtime in config. Replace “available because a0 Deployment” with eas build / submit from a clean checkout. Encode OTA so it stays within the shipped runtime — upgrades still need a new store binary. Fail the pipeline if install only succeeds inside a0’s preview shell.
Mint new backend and payment secrets on destination projects; never commit a0 panel dumps. Point the Expo app at production Convex/Supabase and verify Auth, push, and purchases on a native build — not only web preview. Update deep links and App Store Connect metadata before you freeze the live version. Rotate old a0-visible values after cutover.
Web preview lacks native device features, push, and some native modules; payments and biometrics need IPA/APK paths. CI images lack a0-injected preview assumptions; runtime may drift from what TestFlight has; secrets arrive empty. Normalize Expo install, runtime, and env first. A green react-native-web panel is not a portable store build.
Bring the Expo tree, runtime version, and a few TestFlight accounts. We put owned ship last — and we name the a0 Deployment path you can roll back to.
Prefer writing? Send project details on the contact page.