menu system

Concept 1:

<font color="green">The left side contains the menu categories such as kids adults and desert by clicking on one the right hand side will show you a non detail list of what is in that category by clicking on the item you will get to see a larger description

</font><table style="color: blue" border=2>

<tr><th><h2>good points</h2></th><th><h2>Bad points</h2></th>

</tr>

<tr>

<td>looks organized</td><td>might be to complicated</td>

</tr>

<tr>

<td>Everything is easily accessed by one menu</td><td> Since its a touch screen how can people type in special request <br/> onclick = show on screen keyboard?</td>

</tr>

</table>

Concept 2:

<font color="red">Not really that proud of this one The top allows you to search and then the bottom has a pre-sorted menu </font>

Menu System Sketch (Bin Bao)

Exercise 3: Sketches and Prototypes

I've been sketching prototypes of a menu system based loosely (OK, maybe not that loosely) on Apple's "Cover Flow" interface paradigm, where users—via a touch interface—can manipulate a list of items by swiping left-to-right, right-to-left, etc. I created a quick PICTIVE mockup on posterboard that should get my point across.

--
Wyatt Anderson
wanderson@gmail.com

Sketch Restaurant Menu

Ahmad Abdul Bari Muhammad Firdaus
27047941

I drafter a few sketches based on the knowledge that I know when I shop for things online like ebay and amazon. I come up with a simple structured online menu. On the top of the menu, it has tab for entree, appetizer, drinks, deserts, specials and combos. Once a tab is selected, it will has another tab level that will separate the category of the food. For example, if you click on entree, it will have tabs separated for rice, pasta, spaghetti, pizza and so on. After a category of food is chosen, it will have a list of food on the left with the price. Some list of favorite items might have a small picture of the food. Once a person select an item, the menu would be highlighted and 2 box appeared. The first box has an up arrow icon. When the user click it, it would add up to a chart. The second box does the reverse. When a menu is highlighted, there will be a big picture of it on the right and it has information on that item like description, ingredients, spiciness. A more info button can also be click that would put the user to a more detailed page on the menu. This could include testimonials, and maybe some recommendation that other user like when ordering it. The user can simply click back for going back to the previous menu. Below the description is the cart which has like all the stuff a user wanted to buy. But I think this might be a bad idea as user can simply be overwhelmed by the price and might make less orders. Lastly, there is a submit button that shows that the user are ready to order and that the waiter can just pick it up and start processing the order.

Menu Design

My favorite design was a simple drag and drop interface. I think it would work best for an ice-cream shop like Coldstone where you would drag crumbled Snickers and Oreos into your digital bowl. At the end you would click "Order" and the list of used ingredients would be sent to the workers who would make your custom creation! Another application of this drag and drop could be building a burger (choosing lettuce, cheese tomatoes, bacon etc...) but I think the nature of it is more "fun" and appealing to kids, so I think it'd be best used for creating smoothies and ice creams.

My other designs were based around a division of menu items by "drinks," "appetizers," and "entrees" which I felt wasn't creative enough, no matter how original you make the design its architecture is essentially the same. So I stepped back and used simplicity to break the cycle and the result became my favorite prototype!

-Donato Borrello

Entry #3

I first sketched a few designs without looking at my design ethnography. I wanted to see what I would do without worrying about the details from that report. After reading the report I realized that I left out a few key features in my early sketches. Once I had a design I liked I made some more sketches to refine my ideas. I also made some sketches that showed detailed functionality of on feature of the design. Finally, I made a low-fi design based on my sketches. I will show my sketches and low-fi interface in class.

Nate

Storyboard

I drafted a few sketches based on my design ethnography study of ordering from a menu, as well as from other examples of interfaces designed for the surface PC.  I looked at the tasks that I created in the paper and designed interface features that would help solve those tasks.  Also, because of the large nature of a surface PC I did not restrict my design to windows.  After coming up with a few designs of the parts of the interface, I created a storyboard to illustrate going through the design step-by-step, from sitting down at the table to placing the order.

James J Regan IV
COO Emeritus Consulting
B.S. Computer Science
B.A. Linguistics
University of Rochester
Class 2010

Menu Sketch Descriptions

so, I started off with a more traditional menu--probably because it is what seemed more natural. I created tabs for different pages instead of having the menu scroll. each tab would be named with a category head for each of the spreads of dishes. I also wanted a way for special options to stand out. here I had them have a different background from the rest of the menu in order to create contrast. Finally, the most interesting part of this menu was that you could drag and drop dishes onto a meal timeline to indicate when you want different dishes served.


this next picture tries to highlight different ways to browse a menu. it differentiates with different tabs. the tab shown is the search. it allows you to create lists of ingredients you are interested in and lists of allergens/ingredients you are not interested in. also, there is a considerations list along the side that allows one to drag and drop different dishes onto this list so that one can decide which they want at a later point in time.

finally, here is my last menu. the left panel has the same considerations list that was present in the previous example with the addition of a random selection button. this button allows for one dish in the considerations list to be randomly added to the "receipt" list the center is a list which resembles a more traditional menu. the upper right panel has a place where one may limit the visible menu by different criterium (ingredient desired, allergens, course, et al). finally the lower right panel is the "receipt" list of elements that are to be ordered--with an order button.

- sid