Every phase of Fully Booked had a fixed budget and a founder who needed to be sure it would work for operators. A document describing a feature is easy to misread; a prototype you can tap through is not. So each phase was designed and wired in Figma first, and the founder clicked through it before development began.
A mistake found in a prototype costs minutes, and the same mistake found in code costs days. Working this way kept phases on scope and gave the developers a finished reference for every screen.
### Three files, one productThe work lives in three Figma files, one each for the mobile application, the customer website and the admin dashboard, sharing one set of colour styles and components. An operator moving from the app to a PDF to a business page sees one brand, and a developer building any surface reads the same tokens.
### Wired like the real thingScreens are connected into flows, so tapping a booking opens its details, its route on the map and every state after it. The booking details prototype lays each variation side by side with the paths between them, which is how the founder approved the map screens before they were built.
### Every document, prototyped with the tap that sends itThe document set, quotations, cancellations, invitations, invoices, confirmations and driver sheets, was laid out in Figma with arrows from the app screen that sends each one. The founder could follow an operator's tap all the way to the page the customer receives, and approve the wording at the same time.
### The home screen, tried in variantsThe operator home screen went through several versions in the prototype, each held to the same test: can an operator see what they have earned and reach every way to earn more in one tap. The chosen variant is the one in the app today.
### The business page, before a line of codeThe business page that brought operators direct bookings was designed in full, with fleet gallery, about section, reviews, map, opening hours and booking form, and reviewed as a prototype before any of it was built. The phase that introduced direct bookings started from a page everyone had already agreed.
### The admin and customer website filesThe admin and customer website files hold every page and state, from login to payment, so the web developers built from finished frames rather than guesses. Each phase added its pages to the same files, which keeps the product consistent years later.
### What the prototypes boughtFor the founder, prototypes meant approving features with confidence and paying only for what had been agreed. For the developers they meant no ambiguity, and for operators and customers they meant screens that had been argued over before they reached anyone's phone.
The thinking behind the screens is told in the UI and UX story, and the finished product in the Fully Booked story.