...
- Good: The user used link on splash page to access food page and remarked that it was cool that the tabs at the top updated as well. User felt this provided good visibilty about the page change.
- Good: User enjoyed sorting using the columns on the left and the live search. Commented that this would make a long list of food accessible.
- Good: User had no trouble navigating to the food page and finding the budget. Commented that the graph would be a great visual representation of progress over months.
- Good: The User found the input box for changing the budget in no time.
- Minor: The user tried to click return to submit the form after editing the budget. After a few seconds the user noticed this had no effect and clicked the button to the side of the input box.
- Solution: Implement a key listener to allow for form submission using return.
- Good: User liked that the budget graph was immediately updated to reflect the change in the budget.
- Minor: Editing model is not consistent on the budget page. For updating the budget, you have to click a button to submit the form, while when editing purchases the new amount is saved automatically after clicking outside the input box. The user said this was a bit strange. In neither case, does clicking return submit the form.
- Solution: Again, allow for submission on return key click
- Catastrophic: The user found entering foods (with category, location, etc) tedious, commenting that "I couldn't imagine doing this for every food I buy at Shaws."
- Solution: Include AI to guess category + location or perhaps only show those fields if the user clicks on a button etc. Another possibility is to add food by category (aka enter all the dairy, then all the fruit, so the category only has to be specified once. )
- Minor: The graphics representing location puzzled the user, since names were used in the list displaying food. The user did however understand what they represented.
- Solution: Consider justing using text, or at least having a legion on the add food dialog linking the two representations. (aka, ice cube is freezer . .)
- Minor: The user wanted to set the rice expiration date for a year later, but didn't like clicking through 12 months.
- Solution: Include buttons the calendar that got to a month/6 months/year/never
- Good: User liked that added food was immediately visible, verifying that the add form worked.
- Major: User had to refresh to see recipes page. Had we not been there/had a message, the user probably would have left the site, thinking it was broken.
- Solution: Insure that all content, especially that from external sites, appears relatively quickly.
- Good: The user loved the graphics near each recipe. Without ever reading the name, the user had some idea of what each was for.
- Minor: We display all recipes that our query returns (up to 200 pages). User mentioned that this seemed excessive.
- Solution:Cap the pages of recipe results
- Good: User loved how the search results pointed out ingredients that you would also need to complete the recipe.
- Good: User was impressed by the sorting option on the recipe page and found it easy to specify certain foods and constraints.
- Major: User is not actually able to specify vegan in sorting recipes. The closest you can get is selecting no fish, no shellfish, no meanmeat, and no dairy. Eggs are still included.
- Solution:Use a different external search site, or build a extension that filters out eggs (and find allows users to vegan food without having to select so many buttons)
...