Build Test Lab

booking-app-v1 · run Oct 21, 2026

Bolt.new: 7/8 criteria met

We built the same booking app in Bolt.new that we build in every other builder. Tested Oct 21, 2026 against booking-app-v1.

Criteria met7 of 8
Time to a working deployment16 minutes
Prompts used1
Cost$0.00 (free plan; token usage not shown per build)
Tested onOct 21, 2026

What passed

CriterionResult
A1 — Landing page with all three services and pricesPass
A2 — Booking form: name, email, date, service dropdownPass
A3 — Submitting stores the booking and shows a referencePass
A4 — Booking survives a reload and a new sessionPass
A5 — /admin lists every booking with the key fieldsFail
A6 — Confirmation email sent, or the reason shownPass
A7 — No horizontal scroll at 390 pxPass
A8 — Public URL reachable without loginPass

What broke

Artifacts

Notes

One prompt, one build, 7 of 8. Bolt built the app as a single-page site with hash routing: the booking form lives at /#/book and the admin view at /#/admin, so the /admin path in the brief does not resolve. The booking data does survive a completely new browser session, so it is stored server-side. Email is not configured and the confirmation screen says so explicitly, naming the missing RESEND_API_KEY secret. Bolt also asked its own onboarding survey before the first message could run, which had to be dismissed. The prompt was submitted twice by the automation (editor retained the text), which Bolt handled as one build.

Related answers


How we test and what we do not measure: methodology. Every builder against this brief: booking-app-v1.

Head to head: Bolt.new vs Base44 · Bolt.new vs Lovable