Bolt: build a focused browser-based prototype

Describe a complete activity

Choose a task small enough to finish end to end. A simple expense categoriser, for example, needs an input, a category decision and an editable result. State whether the data is temporary or persistent and which errors should be handled.

Keep the build understandable

Provide real labels and representative examples. Ask the builder to follow the project’s existing stack where one exists. Avoid expanding the scope every time a new screen is generated; an attractive extra section is not automatically useful.

Verify the prototype

Try the core task with ordinary, empty and unexpected inputs. Inspect mobile behaviour and check that controls do what their labels promise. Confirm the product’s current deployment and integration options before planning around them. A browser-based build loop can reduce setup friction, but it does not remove the need to understand data handling and dependencies. The right first milestone is a working experience you can explain and test, not an elaborate interface with unresolved behaviour.

Sources & notes

Source-based guide, not a hands-on product test. Features and availability can change.

bolt.new — official reference

Sources reviewed for the September 2026 launch edition.