Your first app

Best practices for structuring prompts and building your first OpenV2 project.

A great first project starts with a clear, focused prompt. OpenV2 works best when you describe what users see and do, not implementation details.

Start small

Begin with one core screen and one primary action:

Add complexity in follow-up messages instead of one giant prompt.

Describe screens, not code

Instead of…Try…
"Use FlatList with useState""Show a scrollable list of items"
"Add AsyncStorage""Save tasks locally so they persist after closing"
"Create a Stack Navigator""Add a settings screen accessible from a gear icon"

OpenV2 chooses the right React Native patterns for you.

Mention design direction

Reference apps or styles to guide the UI:

  • "Dark theme like Spotify"
  • "Minimal layout like Linear"
  • "Rounded cards with soft shadows"

OpenV2 maps these to your project's theme tokens automatically.

Iterate in passes

A productive flow:

  1. Structure — screens, navigation, empty states
  2. Content — sample data, labels, icons
  3. Polish — spacing, colors, animations
  4. Backend — enable V2 Cloud when you need sync or auth

Use the code editor when needed

For precise changes, edit files directly in the workbench. The AI understands your existing code on the next chat turn.

Common first-app ideas

  • Habit or mood tracker
  • Simple expense log
  • Recipe bookmark app
  • Workout timer
  • Notes app with categories

Warning: Avoid asking for too many features at once. Split large apps into phases — the AI produces better results with focused requests.

Next steps