Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • A slower user, browsed thoughtfully
  • Wanted to explore
  • Felt that location with a lot of restaurants might be harder and take longer to load
  • Wanted one page with all the items, felt it could be hard to remember selections
  • Was confused about how to rotate through menu initially, but got the hang of it after he looked at the arrows
  • Desired price to be in the interface more specifically
  • Passed all the tasks

Initially, we were unsure whether our paper prototypes should be higher fidelity. However, we encountered a couple of groups with higher fidelity prototypes (when testing their prototypes), and truly it was hard for us to give more feedback because we felt they had put in a lot of work into carefully adjusting certain aspects of their prototypes. It was cool to see a lecture-finding applied in real-time.

After the second round, we also asked ourselves a couple of questions that we got as general feedback outside of tasks, and that we might want to add to our next round of prototyping:

  • Should we do mixed grid/scrolling layout - so that people can see what they want more easily?
  • Should our menu be ordered by course - just as it is many restaurants - with appetizers first, main course second, and the dessert third? This might follow a natural progression.
  • Should we have some kind of record feature to allow people to store items they liked so that they can come back it to (or would it burden us too much and distract from the main tasks)?
  • Is price a consideration - should we include some kind of price adder (or would it again burden us too much)?
  • How else can we optimize viewing on a limited experience? Would perhaps the natural affordance of a grid work better? From our original designs, we used the two most riskiest ones for the prototyping round. The second one was more well-received, but perhaps a grid is a more familiar affordance, and users might have an easier time exploring?
  • How can we include pictures more so that users can zoom in more specifically to actually view a dish? Picture-based viewing might be more intuitive.
  • What are other details users want to view for a particular dish?

The two rounds of prototyping definitely provided valuable feedback on what worked and what did not.