Menus, guest ordering, and restaurant operations, built as one connected product.
A later Vividish guest view capture. The guest menu is previewed inside the restaurant workspace; it is not a screenshot of the January build.
The project
A restaurant, on both sides of the table.
A menu is where a guest starts. A restaurant has to keep working after the guest taps an item. Vividish brings the public experience and the operational work into the same product: ordering, reservations, customer context, menus, and the language that guides each step.
My work moves between interface design and the systems underneath it. A payment button depends on an order state. A reservation slot depends on a second check at submission. A useful customer screen depends on knowing when a feature should stay out of the way.
The early work lived in a POS project called Scanwich. The journal follows that lineage into Vividish, keeping each story tied to what was requested, implemented, or still unresolved at the time.
01
The guest journey
Scan, browse, order, follow the order, and pay at the appropriate moment. The transitions matter as much as the individual screens.
02
The operational layer
Menus, tables, reservations, and customer records share state. I investigate the places where independent features create contradictory experiences.
03
The work behind the interface
AI assisted implementation, scoped data access, concurrent writes, bilingual copy, and visual reviews. The journal separates a proposal from a verified change.
Original captures, visible details, and room to look closer.
Screen capture · 21 May 2026The guest view, inside the workspaceA later Vividish guest view capture. The guest menu is previewed inside the restaurant workspace; it is not a screenshot of the January build.Screen capture · 9 Sept 2026Before the order is placedActual Vividish cart component in an isolated development fixture with fictional items and table data. This later capture shows the editing state, not a February transaction.Screen capture · 10 Sept 2026The order has been receivedActual Vividish status component with fictional order data. The development fixture shows confirmation and progress. It does not exercise the February payment path.Screen capture · 9 Sept 2026Reviewing a reservationActual reservation management component rendered in a development fixture with fictional booking data. A later interface example, not a May capacity test or a real guest booking.
