Case study  /  Prototype

One booking, three screens, at the same time.

EBS Bookings. A booking system for party-rental companies: customer site, crew app and owner dashboard.

Role
Product design and engineering
Platform
Web site, crew app, dashboard
Stack
React, TypeScript, Zustand, Vite
Status
Prototype, live
EBS Bookings overview: deliveries today, the amount to collect, bookings for the next seven days, today's route and new bookings from the website.

The project

A simpler booking system for party rentals.

For
Party-rental companies: bounce houses, water slides, tents, tables and chairs.
What it does
A subscription booking system with a real booking website, a crew app and an owner dashboard. All three read one live booking record.
My part
Product design and engineering of the prototype, including three booking-site templates.
Timeline
Prototype, built in one sprint for a client presentation.

The problem

The customer, the crew and the owner saw different things.

A booking taken by phone had to be passed to the crew and written up for the owner. The prototype puts one booking on all three screens at once.

Before

  • Phone bookings
  • Crew messages
  • Separate lists

After

  • Online booking
  • Crew app
  • Owner dashboard

What I built

Customer site, crew app and dashboard.

  • Customer booking site
  • Booking appears instantly
  • Today's route and deliveries
  • Bookings calendar
  • Booking panel with delivery status
  • Inflatables inventory
  • Customers
  • Website from templates
  • Crew app on the phone
EBS crew app: the amount to collect today, the trucks, and the next delivery stop.
The crew app

Results

  • 3screens from one booking
  • Liveprototype

What I learned

One record, many views.

The site, the crew and the owner each need a different screen, but the same booking. Building around that one record kept them in step.