From idea to first build

Every app on DontCode starts at /new. You describe the idea to Insight in a chat, and a side panel fills in as you talk.

What the panel collects

1. Plan: title, overview, features, target users, the user journey, and how the app earns.
2. Design: two or three visual directions with live previews. Pick one and it becomes an editable design system.
3. Files: anything you attach, like a logo or a spreadsheet of products.

Your draft saves on its own. Leave and come back later, on any device, and it resumes where you stopped.

How to describe an app well

Insight builds what it can read. A few habits make the first build land closer to what you meant:

• Name the people first ("customers order, staff confirm, the owner sees totals") so roles and pages fall out naturally.
• Describe one main flow end to end rather than listing every screen.
• Say what is out of scope for now. A smaller first build is faster to fix.
• Numbers help: "about 20 products", "orders close at 9pm".

What happens when you confirm

Confirming creates the real project. The features in your plan become the list on the Features page, the plan and design system are saved with the project and keep steering later builds, and Insight starts on the first build. Builds spend credits; user accounts, sign in, and the database are platform services and never cost a build.

Where DontCode fits

You write the brief; Insight writes and deploys the code. The plan lives on the Design System page under Branding, so when the idea changes, change the plan there and the next build follows it.