Skip to main content
Follow these steps to go from a blank slate to a running Expo app in Openv2.
1

Sign in

Go to openv2.dev and sign in or create an account. Openv2 supports email/password and OAuth sign-in.
2

Create a project from the Dashboard

After signing in you land on the Dashboard at /dashboard. You have two options:
  • New project: Type a one- or two-sentence description of your app in the main input and submit. Openv2 creates a project and opens the workspace at /chat/{projectId}.
  • Existing project: Select a project from your list to continue where you left off.
Keep your initial description brief and focused on the core screen or flow. You’ll refine with follow-up prompts.
3

Learn the workspace layout

The workspace has three main areas:See Workbench & editor and Chat & AI assistant for a deeper look at each area.
4

Send your first prompts

The assistant writes files and runs terminal commands in response to your prompts. Three prompt patterns that work well as starting points:Scaffold a basic structure
Add navigation
Apply visual polish
After you submit a prompt, the assistant may run commands like npx expo install in the terminal before the preview updates. Watch the terminal tab to follow along.
5

Check the Preview

Open the Preview tab in the Workbench. Once the dev server starts you’ll see your app’s web build inside a device frame.
  • If the UI looks stale after a change, use the reload button in the preview panel.
  • For native APIs and real-device behavior, see Test on your device.
The in-browser preview runs the Expo web target. It’s the fastest feedback loop for layout and navigation work.
6

Understand credits

Each completed assistant turn uses credits. Your balance is shown in the header.
  • Free plan: a daily credit allowance
  • Paid plans: larger credit pools, topped up via Stripe
See Billing & plans for limit details and how to upgrade.
7

Review your version history

When a turn finishes and files have changed, Openv2 snapshots the project. You can browse and restore earlier states from the versions panel—useful when an experiment breaks something that was working.See Versions & history for details on how to rewind.

​
Where to go next

Test on your device

Preview your app on a real phone with Expo Go and a QR code.

Prompting tips

Patterns that produce cleaner code and fewer follow-up turns.

Workbench & editor

Explore the code editor, file browser, and terminal in detail.

Versions & history

Browse snapshots and rewind to any earlier project state.