Skip to content
← All projects

Product design · Full-stack · 2026

YakuOrder from the Table

QR ordering for a Peruvian–Mexican restaurant in Hamburg — a photo-first guest app in German and English, and a kitchen screen that receives every order in real time. Designed, built and hosted by me.

Client · Yaku Restaurante, Hamburg

  • Product Design
  • UI Design
  • React
  • Supabase Realtime
  • Postgres RLS
  • DSGVO

Yaku had a strong brand and a great kitchen. Years ago I designed a Mobile Ordering Prototype for them — only visuals. Now it is a working product, tested by the owners with real guests: they order from the table and pay the waiter as usual.

  • My role — design, front-end, back-end and hosting.
  • For — Yaku, a Peruvian–Mexican restaurant in Hamburg.
  • Status — live prototype, tested by the owners.

The original Mobile Ordering Prototype — visuals only Where it started: the original prototype, still only visuals.

Three pieces

Piece What it does
Guest app Scan the table’s QR code, browse a photo menu, add a note for the kitchen, send the order and follow it live. German and English, light and dark.
Kitchen screen New orders arrive with a sound. One tap moves them from new to cooking to served, and the guest’s phone updates on its own.
QR system Every table has a secret code on a printed card. Without it, nobody can order.

Menu in light mode, with Yaku’s canvas texture A dish, full screen Reviewing the order

Light mode uses the canvas texture of Yaku’s own website.

Menu in dark mode A dish in dark mode Live order status

Dark mode uses a warm black that lets the food photography glow — and the status moves as the kitchen works.

Design decisions

  • Photography first — only dishes with a photo are listed, and the menu opens with a Chef’s pick. A menu is a sales tool.
  • Two moods, one brand — a warm black (#121110) that sits well with the dark wood in the photos, and the restaurant’s canvas texture. One accent: ají amarillo, the Peruvian chili, and it always means the next step.
  • A kitchen screen for busy hands — high contrast, large buttons, the table number readable from across the pass, and guest notes highlighted so nobody misses “no coriander”.

The design system

One set of variables for both modes and both screens, documented as a 32-page specimen book: colour with every contrast checked, type, spacing, depth, and each component side by side in light and dark — from the dish card to the kitchen ticket.

The design system: one source for the guest app and the kitchen Every component in both modes: the featured dish

Two brands, one system. The guest app now runs on the same React components as Otra Mesa — buttons, tabs, filters, fields, the language switch — dressed in Yaku’s own skin: its tokens and one stylesheet. Behaviour, keyboard and accessibility are written and tested once; the look stays Yaku’s, pixel for pixel. Yaku has its own living catalogue.

Live from Yaku’s catalogue: a dish with its note for the kitchen. Type in it — this is the component itself, not a picture of it.

View the design system (PDF, 32 pages) ↗ · Open Yaku’s catalogue ↗

The website, rebuilt

Yaku’s website ran on a website builder. I moved it to my own server and rebuilt how it loads — the same look, a fraction of the weight.

Yaku’s website Before After
Total size 134 MB 15 MB
Calls to other companies when a page opens fonts, scripts, maps, booking, video none
  • Lighter — builder leftovers removed, fonts and scripts hosted in-house, every photo recompressed.
  • Privacy first — maps, the booking widget and video load only after a click, and that consent can be withdrawn. Impressum and privacy policy written for the restaurant.
  • Nothing broke — every page photographed on desktop and mobile before and after, and compared pixel by pixel, before the domain moved.

Explore Yaku’s website ↗

Under the hood

Problem How I solved it
Only guests at a table can order A database function checks the table’s secret code and limits how many orders a table can send in a few minutes.
Orders reach the kitchen at once The kitchen listens to order changes in real time (Supabase Realtime).
The kitchen is not an admin Its own role: it can see and move orders, nothing else. Checked with automated tests acting as an anonymous visitor.
Privacy (DSGVO) No accounts and no personal data — a table and some dishes. Everything runs in Germany; demo orders delete themselves every night.

Accessible by default

Checked against WCAG 2.2 AA — the standard behind Germany’s accessibility law (BFSG) — first by a robot, then by hand.

What was wrong What changed
The keyboard focus ring, in bright ají, almost disappeared on the light canvas (1.6:1) Dark ají on the canvas (5.2:1), bright ají at night — fixed once, in the design system
Error messages in a red that measured 3.5:1 A red that passes in both moods (5.4:1 and 7.9:1)
Adding a dish or a new order status happened in silence for screen-reader users Both are now read out
In the kitchen, the focus ring vanished on the cream tickets An ink ring on the tickets

The result: all 12 guest screens clean in light and dark, and a complete order placed with VoiceOver on an iPhone. Accessibility statement ↗

Stack

React · TypeScript · Vite · Supabase (Postgres, Realtime, Auth), self-hosted · Hetzner Germany · Caddy · Otra Mesa design system (shared components)

Next project →Secure & real-time