You sketch the screens, connect them in a design tool, and hand testers something that looks like an app, right up until they tap a button and nothing happens.
To build an app prototype in Bolt.new, you describe the app in plain language and the agent builds a working version while you watch. You refine it by describing changes, then publish it to a live URL with real data and sign-in included. The whole loop fits in one sitting, and no step involves writing code.
What counts as an app prototype in Bolt.new?
In Bolt.new, an AI app builder, an app prototype is a working application rather than a picture of one: as of 2026, the data testers enter lands in a real database, sign-in creates real accounts, and the buttons run the app's logic.
Testers use the prototype instead of imagining it, so they hit problems a clickable mockup can't show. For the full case on working prototypes versus mockups, and how the AI prototyping tool categories compare, see our AI prototyping guide.
You don't need a software background to build this kind of prototype. 93% of small business owners building on Bolt.new aren't professional developers (Bolt.new platform data, 2026). They know their business, describe what they need, and let the agent handle the construction.
What do you need before you start?
You need one workflow, three to five features, and a sentence about who uses the app. You don't need wireframes or a spec.
The workflow is the part to get right. A prototype exists to test whether one job works for one kind of user, so pick the job that matters most and cut the rest. For a tutoring business, that's "a parent books a session." Messaging, invoices, and an app for tutors can wait for a later version.
Then write the prompt. A skeleton that works:
Build a [type of app] for [who will use it]. Users should be able to [core action]. It needs [three to five features]. Include sign-in, and start me on the [main] screen.
Filled in: "Build a booking portal for my tutoring business. Parents should be able to sign in, book a session time, and see notes from past sessions. It needs a calendar, a booking form, and a simple dashboard for me. Start with the parent booking screen."
Don't over-specify. The agent fills in whatever you leave out, and you can change any of its choices later with one sentence.
How do you build an app prototype in Bolt.new, step by step?
The build runs in five steps, and each one happens in the same chat.
Describe the app in one prompt. Paste your filled-in skeleton into Bolt.new and send it. The agent plans the app, builds it, and opens a preview beside the chat, so you watch the prototype take shape instead of waiting on a reveal.
Click through the first version. The preview is a running app from the first build: open it, tap through the core job, and note what's off. Look for gaps on this pass and leave polish for later; a rough screen that works will teach you more than a pretty one that doesn't.
Refine in plain language. "Make the calendar show one week at a time." "Move the booking button to the top." "Parents should get a confirmation screen after booking." Each request revises the same app while you watch. You keep every decision, and a revision costs a sentence instead of a change order.
Add real data and sign-in. Ask for it the same way: "Add user accounts so each parent sees only their own bookings." Bolt wires up a database and authentication, so each tester signs in to their own account and their bookings are still there on the next visit. From here on, your feedback comes from people using the app.
Publish and share the URL. One action puts the prototype at a live link. Send it to five people who match your users. They open the link in a browser; there's nothing to install.
What you have at the end of each step:
| Step | What exists when it's done |
|---|---|
| 1. Describe | A planned build taking shape in the preview |
| 2. Click through | A list of gaps, drawn from the app itself |
| 3. Refine | The app behaving the way you described |
| 4. Data and sign-in | Testers with their own accounts and saved data |
| 5. Publish | A live URL anyone can open |
How do you test an app prototype with real users?
To test an app prototype, send the live URL to a handful of people who match your users, then weigh what they do above what they say. A tester who calls the app "great" and then can't finish a booking has shown you which one counts.
From each tester, note whether they finished the core job without help, where they stalled or backtracked, and what they expected to find that wasn't there. Those answers tell you what the next prompt should fix.
Then fix it the same day. Because revisions happen in plain language, the gap between "a tester got confused" and "the confusing screen is gone" is minutes. Send the fixed version back to the same testers and watch again.
From prototype to product
A Bolt prototype and the product it becomes are the same app: same database, same accounts, same code underneath, growing one request at a time.
The traditional path treats the prototype as disposable: validate with a mockup, then pay US freelance and small-shop development rates of $100 to $300 an hour to build the real thing from scratch (FullStack Labs, 2025). In Bolt, validation and construction are the same work. When the prototype proves out, you keep going: more features, a custom domain, and GitHub sync when a developer or team joins, since the app is standard code they can pick up and extend.
Charlie Revill, a UK manufacturing engineer and self-described non-coder, built E.L.I, a lean-improvement app on Bolt.new in about four weeks while holding a full-time engineering job, then founded a company on it within a month. "I had my own database in Supabase. I had Stripe set up where people could make payments and get access. And it all worked."
Describe your app and start building on Bolt.new for free.
