A mobile knife-sharpening van needs something most booking tools don't do well: customers pick a street stop and a time slot, say how many knives (and scissors) they're handing over, and get a ticket number they show at the van. The owner needs a page with the day's queue that strangers can't open.
I gave that description to NoCoder as one prompt and recorded the whole run. The 40-second cut above is real footage; the build part is sped up 30× and the booking part 2.6× (both marked on screen).
What happened, step by step
- The prompt. Plain English: the business, the stops, the slots, the ticket, the owner page.
- A plan first. Before writing any code it laid out a plan for the app.
- Code, run. It wrote the app and the server that saves bookings, then started it. About 12 minutes from send to "Ready", 43 files changed.
- Checks before "done". This is the part I care about. It ran the type check and the production build, sent requests to the running app, and clicked through the booking flow in its own browser.
- The result. On a phone: pick Northgate Estates, 2:20 PM, four knives and a pair of scissors, get ticket #6. The owner's queue sits behind a sign-in.
What I'd want to know as a buyer
- Did it actually work, or did it just say so? Step 4 is the answer I trust: a real build, a real request to the running server, a real click-through. A summary saying "done" is a claim; those are observations.
- What's fake? Names and phone numbers in the demo are made up (the phone number is from the UK drama range).
You can open the app and the exact prompt in the gallery and try your own: nocoder.codes/gallery/the-grinding-wheel.
What small business would you try this on?
Top comments (0)