A starting prompt
Paste this into the builder and change the names, rules and colours to yours. It produces a working first version; everything after is refinement.
Describe your hours, get the slot logic
The slot grid — which times are offered for which service on which day — is the one piece of real logic in a booking app, and it is where drag-and-drop builders make you fight with formulas. An AI builder just needs the rules in English: opening hours per weekday, slot length, breaks, how far ahead people can book. It writes the function, and if you later say "close on public holidays" or "no bookings less than 2 hours ahead" it edits that one function.
Where do bookings go?
Three options, in order of effort:
- On the phone (default). Bookings save locally; a confirmation goes to you by WhatsApp or SMS from the customer's phone. Good for a single-chair barber or a tutor.
- To a shared sheet. Ask for bookings to be POSTed to a Google Apps Script or a form endpoint. Everyone's bookings land in one spreadsheet you check; double bookings are avoided by reading the same sheet for availability.
- To a backend. Firebase or your own API, with live availability and automatic confirmation. The builder generates the screens and the calls; you set up the project.
Reminders and no-shows
The reminder is a scheduled local notification on the customer's phone — no SMS costs — set when the booking is confirmed. Say how far ahead ("1 hour before" or "the evening before"). If you want a reminder to you, the owner view can schedule one too.
An owner view behind a PIN or fingerprint
Ask for "an owner tab that lists today's and tomorrow's bookings, protected by fingerprint". The builder adds the biometric capability and the exported app declares the biometric permission — nothing else. On a phone without biometrics it falls back to a PIN.