An AI saying "done" tells you very little. The question that matters for a booking site is simpler: what happens when two real people use it at the same time?
So we took two booking sites that NoCoder built from one-paragraph prompts and tried to break them on phone-size screens. Everything below is a real recording of the running app. The names and phone numbers are test data.
Test 1: two people, one mat left
Stillwater Yoga is a class booking site for a small studio: 12 mats per class, a waitlist when a class is full, and a teacher page for cancellations. The prompt included one line we wanted to test directly: "Two people must never get the last spot."
We filled a class to 11 of 12, opened the site on two phones, and pressed Book on both at the same moment.
- One phone got seat 12.
- The other got waitlist, position 1.
- Then the teacher cancelled the booking on seat 12, and the person on the waitlist moved into seat 12 without anyone doing anything else.
The build itself took 13:44 on the run timer, and before it reported done, the agent ran its own race test (12 booked, 2 waitlisted). The gallery page lists that, along with what we found still wrong: right after the build the preview showed an error, which one follow-up message fixed.
Test 2: same barber, same 12 PM
Fade Lab is a booking site for a two-barber shop. Its prompt said: "A barber can never be booked twice at the same time, but both barbers can work at the same time."
Two phones picked the same service, the same barber (Arjun), the same day and 12 PM, and tapped Confirm together.
- One got "You're booked."
- The other got "Sorry — that time was just taken. Please pick another slot."
This race test was ours, run against the finished site. The Fade Lab page is honest about the rest: the prices were made up by the build because the prompt gave none, and the first run hit a workspace that wasn't ready yet.
Test 3: a refresh can lie
This one catches a different kind of fake. Some quickly built apps keep data only inside your browser. After a refresh on the same phone, your booking is still there, so it looks saved. But nobody else will ever see it, including the shop.
So we used a second browser that shares none of the app's saved data with the first:
- Phone B shows Arjun free at 2:30.
- Phone A books 2:30 and gets "You're booked."
- Phone B reloads the page, picks the same barber and day, and 2:30 is gone: the list now goes 2pm, 3pm.
The booking reached the shop, not just one phone.
How to run these tests on any booking site (no code needed)
- The last spot. Fill a slot down to one place, open the site in two windows, and book in both at once. Exactly one should succeed.
- The same resource. For anything with staff or rooms, book the same person at the same time from two windows.
- The second device. Book on your laptop, then open the site on your phone (on mobile data, not your Wi-Fi). If the slot still looks free there, nothing was really saved.
- The cancel. Cancel a booking and check that the slot (or the next person on the waitlist) actually comes back.
It takes about ten minutes, and it turns "the AI said it works" into "I saw it work".
Watch the recording
- Last mat: YouTube Short
Want to try your own? Copy a prompt from the gallery, change the business, and build it free. Then try to break it.
Originally published on the NoCoder blog.
Top comments (0)