How it works
Your project runs inside a WebContainer: a full Node.js environment in the browser tab. When you send a prompt, the assistant edits your Expo project, runs commands likenpx expo install, and starts the dev server. You see the result in a live device-frame preview seconds later.
Projects are saved to the cloud automatically. Every completed assistant turn can create a version snapshot, so you can rewind to any earlier state when an experiment goes wrong.
Who Openv2 is for
- Founders and PMs who need a working prototype without a full engineering setup
- Developers who want AI to handle scaffolding, refactors, and repetitive code
- Teams who collaborate on the same project with editor and viewer roles
What you’re responsible for
Openv2 handles the build loop. A few things stay on your side:- App Store and Google Play accounts — Openv2 supports Expo/EAS-style build flows, but submission is between you, Apple, and Google
- Store policies and review guidelines — review requirements are yours to meet
- Credits — AI usage is metered by credits; see Billing & plans for limits and top-ups
Project structure
Each project has a unique ID and opens at/chat/{id}. The default template uses an Expo file layout with an app/ router and standard Expo config. You work through the Dashboard to create or resume projects.
Where to go next
Validate your idea
Run a quick check before investing time and credits in a build.
Build your first app
Sign in, create a project, send your first prompts, and see a live preview.
Test on your device
Use Expo Go and QR codes to preview your app on a real phone.
Prompting tips
Learn the prompt patterns that produce cleaner code with fewer round-trips.
