...
Shown below is a photo of our summary page:
Design Alternatives Considered:
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.
...
- Correct our accordion behavior for our categories to keep items open once they have been activated once.
Users still unsure how to "go forward" (Efficiency, Minor)
One user wondered around on the pref/restriction page for a good while before clicking on "select restaurants".
Potential solutions:
- Shape the "progression" button as arrows to strongly indicate progress.
- Make the button animate slightly when the system thinks sufficient pref/restriction is being added to notify the user he can progress.
Users are dissapointed when not a lot of menu items show up on menu page due to over-restriction (Efficiency, Minor)
One user restricted a lot of items, and was surprised some of the restaurants has no menu left for him.
Potential solutions:
- Able to rank restaurants by number of safe dishes
- Display on the menu page the hidden items due to unsafe ingredients
Users unsure of what 'plus' and 'minus' icons mean (Learnability, Minor)
One user believed that the green plus would add an item to their restrictions and was confused when it instead added it to the restrictions.
...
- Colorize preference and restriction 'wells' red/green accordingly.
- Explicitly label buttons 'prefer'/'restrict'.
Users liked how polished the UI is (good)
One user said "this is nice, so professional!"
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.
...