Versions Compared

Key

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

GR6 - FoodAware User Testing

Design -

Our application has truly evolved from the start of this course.  Our central problem we wished to solve and the task scenario have remained constant throughout the project. To refresh, the central problem was that people with dietary restrictions have difficulty finding foods.  Our task scenario revolves around a vegetarian that finds it safe to consume chicken perusing a menu and selecting items that he/she wants to eat. 

...

Shown below is a photo of our summary page:

Implementation -

We relied on functionality from Parse to implement our design in order to share data between webpages.  Page logic and interaction is accomplished client side and data such as restrictions, menu selections, and restaurant choice are loaded by querying a Parse account on each page load.

Evaluation -

We tested our implementation on three people.  We allowed each person to choose items pertaining to their dietary restriction and tasked each user to enter their restrictions, browse restaurants and menus, and select items they would like to eat. 

Rez - Chicken Vegetarian

Rez is a chicken vegetarian whose dietary restriction is that he cannot eat meat ingredients with the exception of considering chicken as an acceptable meat to consume.

...

Usability Issues-

...

Other Comments-

...

Kyle - Paleolythic Diet

Kyle is on the paleolythic diet which means that he eats items that are what a "caveman" would have consumed.  He cannot eat products that have been through processing and he cannot grains or dairy products.  He was able to complete the task scenario to completion and print his menu summary for a Kale Salad order.

...

Usability Issues-

...

  • Learnability - (Severity: Minor): He was unsure if on the restriction and preference page he was searching for his preference or restrictions.
    •  Solution: One time viewable alert shown per user to show what functionality is provided for by the search bar.
  • Efficiency - (Severity: Minor): He wanted all the accordions to stay open "to see what I've clicked on." For example, he wanted to keep both the grains and dairy categories to both remain open so that he could scan them both to know all options were selected.
    • Solution:  Correct our accordion behavior for our categories to keep items open once they have been activated once.

...

Other Comments-

...

  • He reinforced our decision to keep a preferences for ingredients in our model by selecting what he wanted to see more of first and then selected his restrictions on the restrictions/preferences page.

Reflection -

With extra time we would have most likely continued using our design and refining it, rather than start a fresh, all-new implementation.  With that said, we have discussed further areas of improvement that we would have liked to incorporate into our design.

...