Omeleth
Summary
Omeleth is an integrated Kiosk + Kitchen Display System for restaurants of any type, combining customer-facing ordering and back-of-house operations through a unified Flutter monorepo + NestJS API. Differentiated by BOH UX research focused on kitchen pressure scenarios, prep-time sequencing and back-of-house legibility. Early MVP code with basic flows scaffolded.
Highlights
Back-of-house UXBOH UX research as the product moat vs commercial KDS competitors
Designs the back-of-house experience around kitchen pressure scenarios, prep-time sequencing and BOH legibility, going beyond the typical 'KDS = order tickets' approach used by commercial KDS systems.
One codebase, two surfaces1 codebase serves 2 distinct surfaces (kiosk + kitchen) via flavors
Unifies Kiosk (customer ordering) and KDS (kitchen) in a single Flutter monorepo with role-based flavors over a shared core layer, instead of two separate codebases.
Six bounded API modules6 bounded modules defined in NestJS API scope
Scopes the API surface in NestJS with bounded domain modules: auth, users, menu, orders, kitchen and analytics.
Sub-second order propagationReal-time order sync via WebSocket between kiosk and KDS
Plans real-time order propagation kiosk-to-KDS via Socket.IO for sub-second order visibility in the kitchen.
Offline-resilient serviceOffline-first strategy for service continuity under network failure
Outlines offline-resilient operation for restaurant continuity when the local network drops during peak service.