GR3 - Paper Prototyping
Prototype photos
Briefing
Hungr is a way to order food with friends. It allows you to make group orders from your favorite restaurants without all the fuss that is usually associated with arranging group orders.
Scenario Tasks
The tasks were presented in the format of a single mission, with the hope that the interface itself would be able to guide the user along.
Users were told:
"You want to order Indian food with your friends Jenny, Pablo, Chris, and Lily, but you aren't sure which restaurant they would like to order from. Place an order involving all of your friends."
The tasks that we wanted them to achieve were to invite friends, choose the category of Indian food, narrow it down via poll with friends, choose food, and submit an order.
Observations
Raw Notes (with summaries at the end)
Day 1:
User 1 Test:
-Looked hesitant without list of contacts (should change for Friday)
-Tried to click "add friends" text
-Easily used checkboxes to navigate restaurant selection
-User chose restaurant rather than type of restaurant
-User having issues using poorly implemented prototype chat box.
-Waits for friends to order (rather than trying to continue)
-Hastily thrown together chat box is causing confusion (no place to type in words).
-Organizer unsure when everyone has ordered. Needs more visibility.
...
User 3 Comments:
-A lot depends on whether or not users are there already
Summary:
-Chat box sucksOur initial implementation of the chat box was hasty and incomplete. Therefore, it was completely unusable until we made corrections.
-Restaurant selection is hazy
-Need It is not clear what options the user has when selecting restaurants (example, just pick one restaurant or pick different combinations of restaurants, and what happens as a result).
-We need to make visible who has ordered and who hasn't, also as well as make it easier to see who is ordering what.
-Need We need to make social aspect more visible as well, as we had people trying to order for their friends.
Day 2:
User 1 Test (little premise given; again, to see user response to lack of information):
Wiki Markup
-"Where's the order button?" (On initial screen, wants to order food right away rather than just select restaurant)
\
-"Are they supposed to be with me right now?" (Referring to friends)
\
-"I think if I'm ordering with friends they'll be right next to me, not on Facebook"
\
-"Oh I could have just clicked \ [send invite\]"
\
-Ok, we really need a better initial explanation, or more affordances for what the user is actually doing
\
-Was under the impression that he was just paying for \ *his food*, not paying for all and running an order
User 1 Comments:
-"Good for company/group meetings"
-Suggested that we have more affordances for "payer" (should indicate that organizer is the one paying)
-Didn't seem to agree with concept.
User 2 Test
...
:
...
\-Invited friends first (rather than choosing restaurant)
\
-"This looks very much like the facebook thing" (in reference to add friends)
\
-"This seems like what I would do to pick the place, but then there's this order thing"
\
-"Don't know if \ [optional message\] is some sort of chat thing"
\
-"Feels strange. Feels permanent." (on send invite)
(At communal restaurant selection)
\
-Torn between clicking "choose" and clicking check box
\
-Notices that his friends are starting to check boxes
\
-"Looks like Jenny voted twice. (oh, they can do that)"
\
-"I'm going to wait for people"
\
-Confused a bit because count looked like radio button (when it was at zero)
(At ordering)
\
-"I want to go family style."
\
-"I was planning on adding this item and then splitting this item"
\
-Splitting seemed to work.
\
-Wait, are we offering splitting to things that have already been ordered?
\
-Sit here and wait. Seems to be a need for check box.
\
-"Pressing \ [review and submit\] will move everyone forward"
\
-Review and submit highlighted
\
-User doesn't seem to be sure what's going on elsewhere. More affordances for done?
User 2 Comments:
-Couple things that didn't seem obvious. If I was invited, done button? After the first time, totally get it. First time, wasn't inherently obvious. Basically, need more affordances for being done.
-Would get the idea with the red and green background thumbnails. However, less obvious of the color change. (when presented with option of thumbnail photos toggling between green and red to indicate "done".
-In the actual menu, maybe highlight things that have been ordered?
-Fairly easy to order family style.
User 3 Test
...
:
-"I guess I want to get Indian" (clicks easily)
-"So, is there going to be a list of Indian restaurants (highlighting fail-prototype didn't include list of Indian restaurants)"
-Tries to initially choose food when viewing menu of restaurant (in initial selection phase)
-Assumes order is saved somewhere
-"Is add friends a link?"
-Tried to hit "Send invite" without adding friends
(At communal restaurant selection)
-"These are restaurants?"
-Seemed to understand after votes began to come in
(At ordering)
-"Now I can order food?"
-"So this is periodically updating? So I have to wait for this thing to be done first?" (didn't seem to get social aspect)
-No affordances for waiting until friends are done. Rather, doesn't indicate what happens if you send an order without everyone ordering.
...
-Forcing to invite friends before ordering. Wanted to choose food first.
-Maybe the initial list wasn't clear?
-Confused by "Invite friends" vs "Send invite". Perhaps Send invite should be grayed out
Summary:
-There are many permanent aspects of our interface that we need to make more clear. Today, we had a lot of people finishing the order before all of their friends had ordered. With our initial design, the other users would basically get kicked out .
-Robot didn't help.
...
of that order (permanent and destructive action). Either we need to find a way to make the permanence more obvious or we need to make the fallback option less destructive (ie, put users who haven't ordered into another order).
-Going along with the first point, users were having trouble knowing when their friends were done ordering. We need a way to make this more obvious.
-2/3 of our users today tried to order their own food before they invited friends. Perhaps we need to make an obvious ordering of steps that's visible to the users at all times.
-We need to prevent premature clicking of "Send Invite".
Prototype iteration
For our second iteration, we expanded the chatbox, and had the orders from the user and his/her "friends" show up in the chat box as they are using the interface, to give them status updates. We also remade the add friends box to be almost exactly the same as facebook's, as this would be more recognizable to the user (and would make sense given our use of facebook connect). In addition, we added expanding panes that would show information about food if you clicked on them, a la foodler.