Your first app
How to write a first prompt that works, and a good order for building: structure, content, polish, backend.
A great first project starts with a clear, focused prompt. OpenV2 works best when you describe what users see and do, not how to code it.
Start small
Begin with one core screen and one main action:
Add more in follow-up messages instead of one giant prompt.
Describe screens, not code
| Instead of... | Try... |
|---|---|
| Naming a specific list component | "Show a scrollable list of items" |
| Naming a storage library | "Save tasks on the device so they stay after closing" |
| Naming a navigation pattern | "Add a settings screen from a gear icon" |
OpenV2 chooses the native iOS or Android patterns for you.
Mention a design direction
- "Dark theme like Spotify"
- "Minimal layout like Linear"
- "Rounded cards with soft shadows"
- "Liquid-glass look, like new iPhone apps"
Iterate in passes
- Structure: screens, navigation, empty states
- Content: sample data, labels, icons
- Polish: spacing, colors, animations (try the Polish the design recipe: type
/) - Backend: add V2 Cloud when you need sync or accounts
Let the agent ask
If your idea is open-ended, the agent may ask a few multiple-choice questions before building. Answer them: it saves a round of corrections.
Pick a mode
For a bigger idea, try Team mode so a product manager scopes the MVP before the engineer builds. See Solo and Team.
Common first apps
- Habit or mood tracker
- Expense log
- Recipe collection
- Workout timer
- Notes app with categories
Tip: Split large apps into phases. The agent produces better results from focused requests.