01The problem
Restaurants juggle a printed menu, a waiter’s notepad, a shouting kitchen and a separate till — so orders get lost, prices go stale and owners only see the day once it is over.
My roleProduct, UX and frontend architecture across six apps — platform console, owner hub, POS, kitchen, waiter and rider — plus the specs for the Supabase backend.
02What I built
- 01Guest QR menu per table with a shared cart for the whole table, allergens and spice levels, “can’t decide? let us pick” and live order status.
- 02Owner hub: today’s sales, a daily brief, monthly goals, orders, tables and floor plans, reservations, menu, packages, promos, inventory, CRM, staff and branches.
- 03Kitchen display with stations (grill, fry, curry, dessert), elapsed timers, bump and sold-out controls.
- 04Phone-first waiter and rider apps with PIN sign-in: table status, bill requests, active deliveries and earnings.
- 05Platform console: MRR, tenants with health scores, subscription plans and invoices, support inbox, feature flags, audit log and a public roadmap.
- 0618 written specs — system overview, schema and ERD, payments and SMS, caching, security and the backend cut-over plan.
03Stack
Next.js 16TypeScriptTailwind CSSnext-intlFramer MotionSupabase
04Milestones
- ✓Guest QR ordering
- ✓Owner hub (14 pages)
- ✓Kitchen, waiter & rider apps
- Platform console & billing
- Supabase backend cut-over
Roadmap65%