PROJECT / VIVIDISH
Vividish
Vividish is the taste thread: every feature exists in a restaurant moment where clarity, trust, and timing matter.
A restaurant operations and guest experience platform where menu, ordering, status, feedback, and website tooling had to feel connected.
ACTUAL PROMPT / THREAD TRACE
make sure every page, every section translation cares about it... written by human who really care about their users.
WHY IT MATTERS
It is a visual product story about making a restaurant OS feel hospitable rather than administrative.
HOW TO READ THIS
Each entry is a dated design decision: the pain point, the response, the proof source, and the visual artifact when the archive had one.
DATED JOURNEY
DATE INDEXPayment and reservation became closeout problems
A restaurant system cannot leave the last step feeling unfinished.
Vividish threads around payment, reservations, and register closeout show the product pressure: every operational edge case is visible to staff and guests.
The design challenge is not adding screens. It is making the last 10 percent of the workflow feel inevitable.
Vividish wiki prompt logs for payment/reservation/register closeout.
Blueprint and production had to match
The app could not look good only in the prototype.
Playwright screenshots compared blueprint and production states across onboarding, PIN, tables, and inventory.
This is visual QA as product discipline: it forces implementation to respect the design language.
Vividish output/playwright blueprint-vs-production screenshots.
The back office became a service map
A restaurant platform has to choreograph the whole room.
Operations, team roles, reservations, register context, directory smoke tests, and website tooling widened Vividish from menu viewer to operating surface.
The interface succeeds when it shows where service is stuck without making the restaurant feel like a spreadsheet.
CHECKPOINT_2026-05-09 and operations screenshots.
The menu became the public product
For guests, the menu is the product. Everything else is backstage.
The cleaned guest menu and live-site fidelity screenshots focused attention on the thing regular people actually touch.
That is why the design language matters: a restaurant app cannot feel like enterprise software at the table.
guest-view-menu-cleaned and live-site-menu-fidelity artifacts.
The copy had to stop sounding generated
Language is product behavior.
Varun pushed for German and English copy that sounded human, useful, and specific to each page rather than AI-polished filler.
This is one of the best signals in the archive: the product is judged not only by features, but by whether every sentence earns its place.
make sure the language of the app doesnt sound AI's but written by human who really care about their users...
Vividish thread: humanize every page, every section, every translation.