The Four Surfaces
One Order, Four Applications, Four Completely Different Jobs
Section 2 of 4
The clearest way to understand this platform is to follow one meal through it. The same order document is created on a phone, worked in a kitchen, settled at a table, reconciled against stock overnight, and counted in platform revenue the next morning — passing through four applications that share almost no interface design because they are used in completely different circumstances.
4
front ends over one API
67
custom back-office screens
2
separate staff authentication flows
1
installable customer PWA
One Order Across Four Surfaces
Colour indicates which application owns each step. Control passes between them without the order ever leaving the shared data layer.
Each Surface in Detail
The diner-facing application is a React progressive web app, and unlike a lot of things described as PWAs it actually is one. It ships a Workbox service worker that precaches the application shell, serves navigation requests from that precache so the app opens without a network round trip, and applies a stale-while-revalidate strategy to same-origin images with a bounded cache so photography does not grow without limit. A web manifest declares standalone display, making it installable to a phone home screen.
That choice fits the use case exactly. Diners open this on mobile data inside buildings with poor signal, and an app shell that renders instantly from cache while content refreshes behind it is the difference between usable and abandoned.
Functionally it covers the whole diner journey: searching venues, browsing a restaurant with its menu and reviews, selecting a table and completing a reservation with a summary step, payment, and a profile area holding order history, favourite restaurants, upcoming reservations, notification preferences, feedback and account deletion.