Imagining the ‘Serve’ App
System Design, User Journeys, Service Design
Serve: Restaurant App
What was my role?
UX Designer
What did I work on?
System Design, UX Workflow, UI Design
What did I learn?
System Design, Scenarios, UI Controls
The Menu
One domain, and setting that generates great interest, is the Restaurant. It is fascinating how the most basic human need to satisfy hunger, has been translated into diverse and exciting culinary experiences, across budgets, cuisines and styles.
Online delivery has become a niche now, and in such a space, it is an interesting question to ask ourselves:
How can the restaurant experience be made more personal?
Who are we designing for?
As I begin, I would love to introduce the characters of this story. They define the way things work, the experiences that we design, and the interactions that need to accompany them.
What kind of Restaurants?
Food, cuisines and the modes of service differ in numerous ways. Each country, region has its own food culture, but for something to be able to scale and match up to the requirements of all the possibilities, it would be essential to dive in to understanding the restaurant space better.
Through not exhaustive, they can be broadly categorised into:
The User Journey
The first step would be to break down the Users Tasks and understand a consequential Behavior Impact on the User.
Mapping out the entire User Journey helps us understand every task the user performs, which have a direct impact on the design of the System.
Key questions:
- What are the different tasks that a User performs when he visits a restaurant?
- How does he/she perform each of them?
- What problems does he/she face?
- Where can we intervene and design a solution?
Problem Definition
Examining the Order Phase
Diving deeper into the user journey, the Order phase gives out some interesting cues in terms of understanding how a User thinks and reacts to situations.
Scenario 1:
While ordering from an endless menu, Aditya is posed with the dilemma of choice: How do I choose from so many? Am I missing out on something?
Scenario 2:
Druva is very fixed about his cuisines and choice of food: I already know what to order. Why am I being made to wait?
Get Krishna Gautham’s stories in your inbox
Join Medium for free to get updates from this writer.
How do we imagine a solution that caters to both these situations (and more)?
Personal experiences have always intrigued tech creators and designers alike.
What do I own? What do I control as a user?
These questions become important in being able to design experiences that suit the needs, contexts and behaviours of a user.
Designing a Personal Experience
The personalisation of the Restaurant experience includes several subjective variables that need to go hand in hand to be able to provide users with the best recommendations and choices.
What affects our food choices?
Variables:
- Cuisine
- Flavour
- Preferences
- Mood
How can Menus be tailored to You, and help make ordering a better experience?
Also, how can the restaurant experience be made to feel like a simple, personal journey?
One way to do it is through helping Users perform tasks based on:
- Context
- Action
- Time
Bridging the Ecosystem for All Users
The platform needs to be able to help both sets of users perform the necessary tasks so as to provide a complete experience. The Restaurant app would contain a Dashboard that works to Receive, Approve and Process orders.
The User App when linked with a Unique Table ID registers a new entry on the Restaurant Dashboard, whose orders are linked to the Profile of the User. This History of Orders helps in learning from the data and providing personal recommendations.
Design Concept and Integration
Choice and Reservation
Check In — Order, Checkout, Feedback
Why Check-In?
- For the User to be able to access the Menu at the present Restaurant
- For Restaurants to be able to match Unique IDs of the Table and the User










