Multi-tenant Booking SaaS
A multi-tenant booking and appointment platform used by barbershops and restaurants in Germany and Switzerland. I spearheaded the React and Next.js frontend.
Senior Frontend Developer
- Multi-tenant frontend
- GraphQL with Apollo Client
- Shared Storybook components
- Booking and appointment workflows
What I personally owned
- Spearheaded the React and Next.js frontend of the booking and appointment platform.
- Introduced Apollo Client for GraphQL data fetching and caching.
- Maintained a shared Storybook component library.
Context
One platform serving multiple tenants across two markets, covering booking and appointment management for hospitality businesses with quite different scheduling shapes: barbershops and restaurants.
What made the frontend hard
Multi-tenancy pushes variation into the frontend. The same screens serve different business types, so the component layer has to absorb that variation without forking per tenant.
- Tenant variation across two business types and two markets.
- Booking data that has to stay coherent while it is edited and re-fetched.
Data layer
Apollo Client was introduced for GraphQL data fetching and caching, giving the booking views a shared cache rather than per-screen fetch logic.
Component library
A shared Storybook component library kept the tenant-facing surfaces consistent and gave the team a place to review components in isolation.
What was delivered
- React and Next.js frontend for the multi-tenant booking platform.
- GraphQL data fetching and caching with Apollo Client.
- Shared Storybook component library.