varun.Product developer
UX designer
← Back to my work

VIVIDISH / RESTAURANT OS

Every table.
One connected
service.

I’m building Vividish so the menu, the room and the people running it can work as one.

Try the handoff Explore the product ↓
Product architectureNative + webService design
vividish.IN THE ACTUAL APP

One workspace.
The whole service in view.

08 OCT 2026
FICTIONAL VENUE

01 / ONE RESTAURANT DAY

The interesting part
is between the screens.

I keep the context moving with the work.

MENU → OPTIONS → AVAILABILITY

The choice needs to be possible.

I connect the guest’s choices to the same catalogue the team works with.

Shared catalogueRequired optionsManual availability holds
Explore this in Vividish ↗
vividish.GUEST MENU

CASA VIVIDISH · EXAMPLE TABLE 8

What looks good?

Real menu selections
€6.90
€7.50
from €1.90
Choose a dish. Explore its ingredients and options.

I selected real items from Zimmer Nr. 2’s menu. Illustrated dishes · local example order.

02 / EVERYONE HAS A PLACE

Six guests.
A room ready.

I turn a reservation into a place for everyone before they arrive.

BEFORE THE DOOR OPENSCasa Vividish / The dining room
Illustrated floor plan
A
Ari’s eveningExample reservation · 90 minutes
Guests
Arrival
01 / Prepare

A little planning. A lot of possibilities.

I tell Vividish which tables my team can join.

T12 seats+T22 seats+T34 seats

One saved group. Every valid subset.

How I find the fit

I start with the tables the restaurant has marked as joinable. I check individual tables and combinations for enough seats and overlapping reservations. The host reviews and selects the fit. The moving furniture illustrates the team’s preparation.

T12 seatsToo few seats
T22 seatsToo few seats
T52 seatsToo few seats
T34 seatsToo few seats
T44 seatsToo few seats
See the actual reservations workspace

Example guests and bookings. Furniture movement illustrates staff preparation.

03 / GO A LITTLE DEEPER

“No added sugar,
please.”

I follow one of two drinks from a request to a confirmed change.

Real menu items fictional service example

Two drinks. One change.

1/6
GUESTTable 08
2 drinks
“No added sugar, please.”1 of 2
01 / AFFECTEDNo’jito1 drink selected
€6.90
02 / UNCHANGEDNo’jitoThe other drink stays.
€6.90
Order total€13.80
KITCHENAt the pass
Team only
TABLE 082 × No’jitoCHANGE REQUEST
NO’JITO
SodaLimeWhite raw sugar ·Mint
PRIVATE KITCHEN NOTE

Waiting for a guest request.

Ready for kitchen review
SERVICETeam queue
Unclaimed
TABLE 081 affected drink1 No’jito stays unchanged
Waiting for kitchen

The request keeps its drink and quantity.

Context travels with the request
Waiting for the handoff

The guest asks for no added sugar in one drink.

Try the actions inside the cards.

04 / LISTEN CLOSER

The dish was ordered.
Was it enjoyed?

I make space for the feedback a guest might never say out loud.

FEEDBACK AS IT ARRIVES

Every voice adds to the picture.

Month in view
NO NAME REQUIREDPrivate feedback
A guest at T11Sep 30 · 19:47 · Example
◡Not my taste
THE DISH THEY RATEDRed Heat
◡Not my taste✓Good♡Loved it
“The heat hid the other flavours.”
Not my tasteResponse received. Dish stats updated.
I keep the guest’s voice private and the dish signal useful.
SEPTEMBER · EXAMPLE MONTHEvery day tells me more.
30/ 30
Daily Red Heat orders and dish responses
Red Heat
1,000orders with Red Heat
/
50direct dish responses
5% response coverage950 unmeasured
35Not my taste
11Good
4Loved it
THE MENU, IN MOTIONSimulated updates

Different dishes.
Different stories.

Red Heat1,000 orders50 ratings
5%rated
Queen Mozzi800 orders64 ratings
8%rated
No’jito1,200 orders48 ratings
4%rated
THE PATTERN IS WORTH A LOOK35 of 50 responses say “not my taste”.

Repeated comments about heat give my team a recipe to review. The other 950 orders have no measured opinion.

MY TEAM MAKES THE CALL
30 days. A clearer view of the menu.Fictional guests · simulated live updates
How I read the signal +

I keep visit reactions and directly rated dishes separate. This example shows 30 days of fictional orders and responses across three real menu selections. Response coverage is measured opinion, not proof that everyone else enjoyed the dish. The restaurant chooses whether to review a recipe or place a manual hold. The actual report refreshes while in use; this animation uses local example data.

Actual feedback report ↗

6 October 2026 · Isolated QA venue · Separate small response set

05 / IN THE SHIFT

Run the shift.

I keep the work moving, one ticket at a time.

vividish.CASA VIVIDISH / EXAMPLE SHIFT
CASA VIVIDISH

Orders

5 active · longest wait 14m

19:24
New 2Waiting to send
3 min
#1042 · RegisterNew
  • 2×
    Margherita
1 min
#1043 · RegisterNew
  • 1×
    Queen Mozzi

    No rocket, please.

  • 1×
    Blueberry No’jito
Sent 0With the kitchen
Nothing waiting here.Send a new ticket to bring it here.
Preparing 2Work in progress
6 min
#1048 · RegisterPreparing
  • 2×
    No’jito
  • 1×
    Red Heat
14 min
#1046 · RegisterPreparing
  • 2×
    Queen Mozzi
Ready 1Ready for the table
9 min
#1051 · RegisterReady
  • 2×
    Tafelwasser
Try a ticket. The whole order stays in view.

I rebuilt this screen from the Orders interface for this story. Fictional shift · local controls.

WHAT THIS SHOWS

I build the connections
that make a product feel whole.

I follow the small details from the guest’s screen through the team’s work.

Explore Vividish ↗
About these screens and examples

I selected actual app captures with fictional venue data. The selected workspace views were captured on 8 October 2026, with the feedback view from 6 October, in isolated local previews. They show real native components rendered on the web with fictional venue data. Each workspace keeps its selected snapshot version.

I selected real menu items from Zimmer Nr. 2’s published menu for the interactive menu and fictional service example. This example does not establish a customer relationship. The reservation scene illustrates staff arranging the room. The handoff, Orders workspace and feedback cards use fictional conversations, example bookings and simulated order counts. I rebuilt the Orders controls in this page from the app’s interface and rules. The example menu order stays in this page. These controls do not make bookings, send messages, change stock or take payments. These web renders do not establish acceptance on a physical phone.

I checked the current source and the public product site while preparing this showcase. Vividish continues to evolve.

Actual app capture · fictional venue data · local web rendering