APP DESIGN
A table ordering app for the restaurant Sushi Train
The team
Olivia | User research, Wireframing, Prototyping, Visual design
Angela | User research, Wireframing, Visual design, Coding
Shawn | User research, Coding
Project objectives
-
Enabling customers to order easily
-
Enabling customers to see the progress of their order and view deals
-
Encourage customer suggestions and input
USER RESEARCH
To understand user’s needs and attitudes when they are using ordering apps
-
Method | Survey
-
No. participants | 27
-
Time frame | 3 days
Survey data
Positives
-
Order at their own pace, get more time to make decision
-
Less contact with the staff
-
Easy to use
-
Don’t need to queue for ordering food
Pain points
-
Difficult to ask staff questions, prefer human interactions
-
Laggy
-
Bad UI, too much text
Key features users would like to see
-
No lag time
-
Menu ingredients
-
Photos for each dish
-
Language options
-
Easy to use
-
A notes section for any special requests
-
option to call a staff member if you have questions
After organizing the data, we summarize them into 4 types of users. We then created an empathy map and personas for the 4 types of users.
Team collaboration via Google Jamboard
After understanding the user, a journey map is created to analyse user’s habit.
SITE MAP & STYLE GUIDE
ITERATIONS
Each of the team members created a set of wireframes then presented the wireframes to the team. We then gave feedback on each of them.
1st Iteration
User testing
Content
-
No clear price on the menu
-
No clear total quantity on the cart
-
No previous ordered items
-
The social media section of the rating page is redundant
-
The “help” button is not obvious
-
They need an incentive to give a rating
Navigation
-
Users don’t know when to use the finish button
-
The timeline is confusing
Functions
-
Users want a order more button
-
Need a pop-up window to confirm calling staff
-
Need a pop-up window to confirm finish dinning
2nd Iteration
-
Revised the wireframes according to the user’s feedback
-
Added new pages and pop-up windows
User testing
Content
-
Can use a symbol to represent the “cart”
-
The previous order button is not obvious
Navigation
-
Users think they may not notice the “ready to pay” button when they finish dinning
-
Users thought the timeline was clickable
