Menuvyn

02The challenge

The challenge

Restaurants need to update menus, take table orders and keep the kitchen informed. A static PDF menu cannot handle that workflow, and dedicated hardware adds another cost.

03The thinking

Roads taken, and the ones that weren’t.

1. 01

   Took

   Real-time collaborative group ordering for tables via WebSockets.

   Instead of

   Isolated individual diner carts requiring separate orders per person.

   Because

   Diners at the same table can add items to a shared order and see who added each item before submitting it.

2. 02

   Took

   Dual ordering architecture: direct digital kitchen submission and offline-capable Waiter QR Dockets.

   Instead of

   Mandating tablet hardware in the kitchen before any orders can be placed.

   Because

   A waiter can scan the diner's order, including modifiers and totals, without requiring a kitchen tablet.

3. 03

   Took

   In-browser Web Audio API alert synthesis for kitchen display chimes.

   Instead of

   Streaming external MP3/WAV audio files over the network.

   Because

   Generating the chime in the browser avoids a separate audio download. Playback still depends on browser audio permissions.

4. 04

   Took

   Trilingual content model (English, Sinhala, Tamil) as first-class entity fields.

   Instead of

   Automated browser translation plugins (Google Translate).

   Because

   Authored fields let restaurants supply dish names and ingredients in each language, rather than relying on automatic translation.