...
- Can become a problem if patron is actively searching for a menu item
- If multiple suggestions of the item is rejected, the patron will become impatient
Wei
...
:
...
Design Sketches:
#1. Server side can update menu, add new meal and review before submission. For patron side, patrons can save meals and review chosen meals.
...
#3 Stretched Design for children.
Trying to make the design as simple as possible . while also keeping the food safety issue in mind.
Use big images and immediate visual feedback to make it affordable to children.
Patrick: (add more designs/sketches here, if you have any, keeping the format as the items above)
Group Designs
After merging our individual designs, we present these designs as a group:
...
The flow here is designed to be similar to a shopping cart, with entering of dietary restrictions and preferences kept separate from food selection. We also provide here a 'summary' view at the end so that users can view all the food that they have chosen and see the total price. We also use text entry as opposed to pictorial selection to choose allergens/preferences.
Storyboard -
First, server use FoodAware to update menu. They can upload a picture of the meal, enter the name and price of the meal. They can also choose from a list of ingredients from the ingredient box (forgot to draw it there). Each ingredient will have a check box in front of it. If some ingredient is not there, they can enter it by text. They do the same for the substitution. Choose it from a list of ingredients, and if it is not in the list, they can enter it manually.
Then we move on the patrons side, who will be browsing either at home or at the restaurant. Patrons can choose to enter food allergies/preferences first by text. They may also choose to skip the section. As they enter the food allergies/preferences, they will be able to see the direct visual feedback on the right. We will implement auto-complete to help the user to enter the choices. The idea is to keep it simple, so that users don't have to search from a long list of possible food allergies. We assume that most people are not allergic to too many food items.
After the two steps, patrons can proceed to choose from the filtered menu. Each item would have a check box in front for the user to save it. They can also review their save items by clicking the Like_List button, which will bring up a window for them to do a final modification. They can also sort food by different categories such as price/preference/calories/chef_recommendation and so on. They may also search for a specific item they really like. Maybe Sarah really wants to check all the item that has fish in it. If the view button is clicked, patrons will see a full image of the food, with a full list of ingredients. Substitution availability would also be made visible. They will be highlighted for the patrons.
After the patron is satisfied with her/his choice, she/he can save the list and order food.
Pros:
- Text entry obviates the need to hunt through a list of pictures to find their allergens/preferences
- Save user profile allows for tracking of preferences over time.
- Many opportunities allowed to fix an incorrect entry for a safer design. For example, the user can remove items from the queue on the "checkout" screen.
...