Quickstart: ship your first Builder app
This quickstart is for teams using the hosted OXVO Builder product for the first time.
Before you start
- You can sign in to an OXVO workspace with Builder access.
- Your workspace has at least one managed model provider enabled, or you know who can enable it.
- You have a clear first app idea or a GitHub repository you want to import.
Step 1: Launch Builder from OXVO
- Sign in to OXVO.
- Open the left sidebar.
- Select OXVO Builder.
- Confirm the workspace name in the Builder top bar.
Tip: If you open Builder directly and you are not signed in yet, Builder routes you back through OXVO first.
Step 2: Create or import your first project
Choose one starting path:
- Start from a prompt if you are building a new app
- Import Repository if you already have code in GitHub
In hosted Builder, import is GitHub-first. Local folder import stays outside the hosted workflow.
Continue: Create, import, and manage projects
Step 3: Write the first build prompt
Use a prompt that gives Builder enough product context to make good decisions.
Good first prompts usually include:
- what the app is for
- who will use it
- the core workflow to get right first
- the visual direction or tone
- any required integrations or data needs
Example:
Build a customer onboarding dashboard for a B2B SaaS team. Include a clean overview page, account checklist, task detail panel, and activity timeline. Keep the UI calm and operational, not marketing-heavy.
Continue: Build with AI Chat
Step 4: Review the first result in preview
When Builder finishes the first pass:
- Open Preview to inspect the live app.
- Open Problems to check build or runtime issues.
- Open Code if you want to inspect the generated structure.
- Use follow-up prompts to refine layout, flows, and copy.
If the preview is healthy, you can also use Edit component or Select components for targeted visual changes.
Continue: Review preview and visual editing tools
Step 5: Save reusable work
Once the app starts looking right, capture anything you will want again later:
- save the app as a Template
- store reusable instructions as Prompts
- save a reusable visual direction as a Theme Prompt
Continue:
Step 6: Add backend features only when you need them
If your app now needs auth, database tables, uploads, secrets, or server-side routes, turn on Builder Cloud for that app.
Continue: Use Builder Cloud for backend features
Step 7: Connect publishing tools
When the app is ready to share:
- Connect GitHub if the app is not already linked.
- Add collaborators if needed.
- Connect Vercel from the Publish panel.
Continue: Publish and deploy Builder apps
Recommended first-session outcome
By the end of the first session, aim to have:
- one working app in preview
- one clear follow-up chat for refinements
- GitHub connected if the app matters long term
- Builder Cloud enabled only if the app truly needs backend features