How to use Startbase

From idea to working app

Plan before you prompt, choose the right build order, break work into bricks, and validate with real users.

You have an idea and you know exactly what you want, but the gap between inspiration and a working prototype can feel huge. This guide closes that gap with a repeatable process that works whether you are technical or not.

Plan before you build

The most common mistake is jumping straight into prompting before clarifying what you are building. The result is errors on top of errors, confused AI output, and projects that feel "too far gone to fix."

Before you open Startbase
Spend 15 minutes writing down what the product does, who it is for, and what the simplest possible version includes. Turn that into a bullet list of features and feed it into Plan mode or an external AI to draft a rough product brief.

Choose your build order

There are two valid strategies:

Frontend first (recommended for beginners): Build layouts, flows, and logic with mock data. Once the UI feels right, connect your database and go live.
Backend first: Enable Cloud on day one and build each feature end-to-end. Best for experienced developers comfortable with SQL debugging.

If you are new to Startbase, start frontend-first. You will iterate faster, avoid complex schema errors, and stay focused on design and usability.

Break it into bricks

Do not try to build everything at once. Split your idea into bricks: each brick is one feature, one component, or one user flow. Build one at a time, test it, then move on.

Example breakdown:
1. Create the layout and pages
2. Add the UI components
3. Wire up state and data
4. Handle edge cases and validation
5. Test per user role

Escape the error loop

Clicking "Try to Fix" ten times in a row rarely works. Instead, open your browser dev tools (Console tab), copy the actual error, and paste it into Plan mode so the AI can investigate properly.

Startbase reads console logs automatically in most cases, but pasting the raw error yourself gives the agent the clearest possible context.

Validate with real users early

Do not wait for perfection. Share a preview link with five or ten people and ask "Would this help you?" Real interest, not polished pixels, should guide your next steps.

Builder's checklist

Write your idea in 5-10 bullet points.
List core MVP features.
Decide: frontend first or backend first.
Use Plan mode to co-plan and debug.
Build in bricks, one feature at a time.
Connect the database only when the UI is stable.
Restore a checkpoint if errors start cascading.
Collect feedback before going live.