02 / 05Appointment booking for service businesses2026
Waeda
Customers book from their phone with no account, and an appointment guard keeps booked times from going empty.
- Laravel 12
- MySQL
- Vue 3.5
- Vite 6
- Tailwind 4
- Pinia
- PHPUnit
- Vitest
- Playwright
- PHP 8.2
- Sanctum
- REST API
- Chart.js

At a glance
01Who is it for?
- The business: a clinic, salon, training centre, home service, restaurant or court.
- The front desk: they drag bookings to new times, add bookings, and answer the replies the guard could not read.
- The customer: books with a phone number and no account, and can move or cancel later.
Before the project
For a clinic or a salon the real loss is not too few bookings but the booked time left empty when the customer does not show. Customers do not want an account just to book one appointment, and a working day in the region has its own rules: hours past midnight, Ramadan hours, prayer times.
- Paid time wastedA no-show leaves the slot empty, with nothing to make up for it.
- Two bookings, one timeWhen two people confirm the same slot in the same second.
- Tools that do not know the regionNo hours past midnight, no Ramadan, no prayer times.
The product
The product, as its users use it
Scroll to walk with the user one step at a time, each step on the screen where it actually happens.
Your booking page
The business picks one of six ready sectors, and its own booking page builds itself.
/register

Book from the phone
The customer picks a service, a person, a day and a time, and confirms with a phone number, no account.
/b/alrayhan

The day on one board
One column per person, a live line for now, a queue of what needs action, and drag to move a booking.
/app

The appointment guard
The customer replies 1 to confirm, 2 to cancel or 3 to move, and a cancelled slot is offered to the waitlist.
/app/guard

Bookings and customers
Tables that sort and filter, and each customer’s history and no-show rate.
/app/bookings

The month in numbers
Occupancy, revenue, no-show and cancellation rates, and demand across the hours of the day.
/app/analytics

How it was solved
Built to hold
The decisions that make the promises above true, rather than a look on the screen.
The lock where it counts
The API locks the resource row and tests for an overlap inside the transaction that writes the booking, so the second one always loses. Overlap is half-open: a booking ending at 10:00 and one starting at 10:00 do not collide. A test with two live concurrent connections proves it instead of a comment.
The business’s clock, not the visitor’s
The business carries its time zone, and the guest pages put their dates on that clock, so the same code computes and shows the business’s wall-clock times wherever the guest is, and times reach the server as plain UTC.
Proof, not a guess
The phone code used to be made and checked in the browser; the server now issues and checks it, with limits on attempts. Managing a booking takes a random secret link stored hashed, or the whole phone together with its proof, and cancel and reschedule ask for the same.
Worth explaining
A guard that holds
Before releasing a booking nobody answered, it re-reads the row under a lock and gives up if the customer confirmed in the meantime. One business’s error no longer stops the run for the others, and the language model has an eight-second timeout before falling back to word lists.
The server sets the price
Length and evening-peak pricing are computed on the server, and whatever price the browser sends is ignored. The rule exists in both the browser and the API and both are tested against the same cases, so the demo and the real backend agree.
A full review, every finding a test
The whole project went through a review, and every critical or high finding was first proven with a failing test, then fixed until it passed, and the tests stayed. Today: 217 PHPUnit tests on a real MySQL database, 197 Vitest tests, and a Playwright walk through every screen that fails on any console error.
The outcome
What was delivered
- 12
- screens in the product
- 16
- real screenshots
- 414
- automated tests
- 2
- full languages
- A live demo with no sign-up, and one button into the console with a demo account.
- 217 PHPUnit tests on a real MySQL database, 197 Vitest tests, and a Playwright walk through every screen.
- Six ready sectors, prayer pauses for 20 cities, Ramadan hours dated by Umm al-Qura.
- Free, Basic and Pro plans with a 14-day trial.
- PASSTwo operators confirm the same slot in the same second: the second one losesbooking/tests/ConcurrentBookingTest.php
and 413 more in the repository
Every screen
Every screen, as it is
Real screenshots of the project running — not stock imagery.
Every page in the project
Real screenshots of the project running — not stock imagery. · 16 screens





