Problem
Deeva sends hairdressers, beauticians and make-up artists to the customer’s home. Bookings used to happen on WhatsApp. The customer wrote a message, and the staff checked availability and confirmed by hand.
The goal was a booking flow customers could finish on their own. They pick an address, the services, a professional and a time slot, and can apply a coupon or a gift card. A group flow handles bookings for several people at the same address. Payment happens at the appointment, by card or Satispay, so the app never handles it. Customers also get a personal area with their bookings and details.
Architecture
It’s a single-page React app hosted on Render, talking to Deeva’s REST API with a bearer token. The router loads the session before the first render. Google Places completes the address, GTM and VWO handle tracking and A/B tests, and Trustpilot shows reviews. When a booking is created, the API returns the URL of the confirmation page.
Scope
Mine
- The booking app: the four flows, the checkout and the personal area
- A typed client with Zod validation on about 20 endpoints
- Session and data loading in the router
- Analytics events tied to each step of the funnel
Other teams
- REST API and data model (Deeva)
- Tag configuration and A/B tests (Linko Digital)
Key decisions
One pattern per domain: schema, service, hook
Why. The API changed often while I was building the app. I put every response through an Axios wrapper that parses it with Zod, so the types match what the server sends. Each domain has the same three files, which makes a new endpoint quick to add and easy to review.
Trade-off. More boilerplate per endpoint. A failed parse also stops the screen, and any mismatch with the backend has to be fixed before it ships.
Generate the funnel routes from a typed list
Why. The four flows share most of their steps, but not all of them. I generate the routes from one list, and TypeScript derives the valid URLs from it. Link to a step that doesn’t exist and the type check fails. Dropping a shared step from a flow takes one line.
Trade-off. The config is abstract. A new developer has to read the types to see the full list of URLs.
Load the session in the router
Why. The router loader fetches the user before the page renders and puts it in the TanStack Query cache. Pages read it from the cache, so the user is already there on the first render and gets fetched only once.
Trade-off. The token lives in localStorage. That’s simple, and it also means any script on the page can read it.
In code
The funnel routes, with one flow written out:
const mainRoutes = [
"location",
"participants",
"participants-salotto",
"category-salotto",
"category",
] as const;
const flows = [
{
flow: "beauty",
routes: [
...withoutSteps(mainRoutes, ["category-salotto", "participants-salotto"]),
"/booking/beauty/service",
"/booking/beauty/address",
"/booking/beauty/data",
"/booking/beauty/checkout",
],
},
// hair, make-up and the group flow follow the same shape
] as const;
// Every valid URL, derived from the list above
type FlowRoute = (typeof flows)[number]["routes"][number];
const next: FlowRoute = "/booking/beauty/checkout"; // ok
const typo: FlowRoute = "/booking/beauty/payment"; // type errorResults
- 4
- booking flows (hair, beauty, make-up, group) from one typed route list
- ~20
- API endpoints behind a validated client
- 713 / 751
- of the frontend commits are mine
Customers now book without writing to the staff. The app has been in production since 2024, and in 2026 the client’s own developer started working in the codebase. An A/B test has been running on the funnel since March 2026.