QuickByte is an ordering system for use in restaurants to automate and streamline the dining experience.
Knowledge: User Interface Design • Interaction Design • HTML/CSS
Tools: Notepad++ • Photoshop • Paper Prototypes • FinalCut Pro • Contextual Inquiries
Website: QuickByte
THE PROBLEM
The popularity of technology replacing humans in the workplace has grown significantly over the years and one industry that has a significant potential to integrate machines in their daily operations is the food service industry.
1. At a restaurant the food ordering process can cause confusion and ambiguity
2. Language barriers and unclear menus pose health hazards and unexpected results
3. The payment process can be frustrating
THE CRITERIA
1. Create an electronic system that can essentially replace a server at a restaurant
2. Be user friendly and convenient regardless of technical ability
3. Operate on any portable platform (tablet, smartphone, kiosk)
THE MOTIVATION
I created this user interface because I identified the food industry being a bit inefficient in the entire dining process for a patron. I understood that many people like to dine out for the simplicity of being served by a human, however QuickByte would be an option to streamline the experience. Some reasons why I was motivated to create QuickByte are:
1. Wait times, reservations and intital contact with the server was wasting a lot of time
2. Unclear menus, vague food descriptions and language barriers meant frustration
3. The payment process can be awkward and time consuming
4. I cannot immediately review the food when it's fresh on my mind
THE SOLUTION
QuickByte is a software application that runs on a portable device such as a smartphone or tablet. As soon as a diner walks into a restaurant, they can use their own smartphone or use a provided tablet and log-in to the QuickByte interface.
The application will allow you to do the following:
1. Customize and order varieties of food (appetizers, mains, dessert, drinks)
2. Determine the status of food preparation
3. Pay and review for their food electronically
And just as a precaution, if at any time a user is lost, there is a "Help" button at every step that will immediately call a server
Here is a video created to showcase QuickByte in action at a restaurant:
There were many iterative steps taken in creating QuickByte. After researching multiple users and getting industry feedback I created multiple prototypes including paper prototypes. Below is a look at our wireframe prototype of the interface created using Balsamiq:
After multiple iterations and revisions of user-testing the wireframe, I created the functional prototype of the GUI:
This storyboard below shows a typical interaction scenario of a user with the QuickByte system:
In addition to doing storyboarding, I also like to use post-it notes to figure out all my customer's needs, wants and experiences. Using sticky notes is a great way to brainstorm and iterate on various ideas:
Back to Top
Knowledge: User Interface Design • Interaction Design • HTML/CSS
Tools: Notepad++ • Photoshop • Paper Prototypes • FinalCut Pro • Contextual Inquiries
Website: QuickByte
THE PROBLEM
The popularity of technology replacing humans in the workplace has grown significantly over the years and one industry that has a significant potential to integrate machines in their daily operations is the food service industry.
1. At a restaurant the food ordering process can cause confusion and ambiguity
2. Language barriers and unclear menus pose health hazards and unexpected results
3. The payment process can be frustrating
THE CRITERIA
1. Create an electronic system that can essentially replace a server at a restaurant
2. Be user friendly and convenient regardless of technical ability
3. Operate on any portable platform (tablet, smartphone, kiosk)
THE MOTIVATION
I created this user interface because I identified the food industry being a bit inefficient in the entire dining process for a patron. I understood that many people like to dine out for the simplicity of being served by a human, however QuickByte would be an option to streamline the experience. Some reasons why I was motivated to create QuickByte are:
1. Wait times, reservations and intital contact with the server was wasting a lot of time
2. Unclear menus, vague food descriptions and language barriers meant frustration
3. The payment process can be awkward and time consuming
4. I cannot immediately review the food when it's fresh on my mind
THE SOLUTION
QuickByte is a software application that runs on a portable device such as a smartphone or tablet. As soon as a diner walks into a restaurant, they can use their own smartphone or use a provided tablet and log-in to the QuickByte interface.
The application will allow you to do the following:
1. Customize and order varieties of food (appetizers, mains, dessert, drinks)
2. Determine the status of food preparation
3. Pay and review for their food electronically
And just as a precaution, if at any time a user is lost, there is a "Help" button at every step that will immediately call a server
Here is a video created to showcase QuickByte in action at a restaurant:
There were many iterative steps taken in creating QuickByte. After researching multiple users and getting industry feedback I created multiple prototypes including paper prototypes. Below is a look at our wireframe prototype of the interface created using Balsamiq:
After multiple iterations and revisions of user-testing the wireframe, I created the functional prototype of the GUI:
This storyboard below shows a typical interaction scenario of a user with the QuickByte system:
In addition to doing storyboarding, I also like to use post-it notes to figure out all my customer's needs, wants and experiences. Using sticky notes is a great way to brainstorm and iterate on various ideas:
Back to Top