GR1 - MenuMe

Anthony Chen, Andrew Cooper, Ben Stueck

Our population consists of mobile phone users in need of finding a restaurant who are divided among two different groups.

User A is with small group of friends who have just finished watching a movie at the theaters. They decide it is time to get some dinner but the group cannot quickly come to a consensus for a place to go. They brainstorm for a couple minutes, but eventually they decide to use their mobile devices to begin searching for restaurants nearby. As they look into the options, they are only able to pull up two different menus before the group becomes antsy, and chooses the first idea to save some time.

We discovered this user class when one interviewee discussed the difference between using a food finding application at home and on vacation.  He mentioned that while on vacation he might be searching for any restaurant to go to.  While at or near home, though, he may be jogging his memory of what options are available, since presumably he “knows” the restaurant landscape.  This latter case is discussed here.

User B is a visitor on Newbury Street who has decided its time to get some lunch. She has not made any plans for food, and needs help to make a choice. She wants something quick and nearby, but she also knows that she is a picky eater and needs to see her options before going in. As a result, she decides her best option is to visually locate the restaurants she can see around her, and make a choice when she sees the first menu that satisfies her preferences.

2 of the 3 interviewees discussed that in an unfamiliar setting they will not use any application to locate a restaurant, as the applications they are familiar with are too cluttered and obnoxious to use. Instead, they will just do the best they can on their own.  When probed about whether they would use a “good” application, both said they would be very open to using technology in an unfamiliar setting. This use case above is a person that might be in this situation.

User C is driving with his girlfriend to visit her family. They are in the middle of a long the ride when they decide they need a break to find a nice meal. As they use their mobile device to look at restaurants, they frustrated with the number of restaurants they can compare at a given time. The current network conditions make it difficult to look at many different pages in search for the best menu. Eventually, the coupled decides to settle to eating at the next exit.

One interviewee asked about whether our potential application would refresh if he moved while using it.  Although we haven’t decided that, it did bring up this interesting case, where a user is in a car and is traveling through a lot of space per unit time.

These tasks were the three main tasks our interviewees discussed as being most important to them in a restaurant finding application.  We feel that these three tasks would make for a complete application.

Goal: Easily find restaurants that are enticing to the user.

Our application optimizes this search by compiling an aggregate menu of all nearby restaurants, based on the user’s GPS coordinates.  It then selects the most popular dishes at each restaurant and builds a menu of them.  Users use this menu to select a restaurant they are interested in.

Tasks in finding a restaurant:

  • View an aggregate menu of all nearby restaurants.
  • Navigate this menu and select dishes that interest you.
  • View full menu, prices, and ratings of selected restaurant.

Goal: Simply and easily compare two restaurants side-by-side.

Our application allows users to compare two restaurants on the basis of particular dishes the user wants to eat.  It compares these dishes, then factors such as location of restaurant, rating of restaurant, etc.

Tasks in comparing restaurant menus:* Choose restaurants to compare

  • Simplify the information provided for the user
  • Provide the user with adequate information to make a decision

Goal: Help the user find their way to the restaurant of their choice.

After deciding on a restaurant to eat at, our application will guide the user to his destination. Using their current GPS coordinates, the app will provide directions to the restaurant depending on the mode of transportation.

Tasks in commuting to restaurant:

  • Find directions from current location
  • Display travel information: route, time

TA Feedback.

As we discussed in our meeting, this project is just barely a stretch. Try broadening the user population, and make sure it's not just a layer over a database.

You don't seem to really get a good feel for what the tasks your users use to solve your problems, and instead you describe actions that your app will let users take. Don't forget that the next step is to make three separate designs - you shouldn't already have picked one. Think of task analysis as the analysis of tasks that need to be done to solve the problems. For instance, why use menus to compare restaurants? Why not Yelp ratings?

Please change the name of your group to something consistent with the project. I'd appreciate it if you made these changes, since we'll be working off this document for the whole rest of the project.

  • No labels