Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

In task 5, many users didn't understand the delete functionality and the fact that there was a list of deleted items. We reworded the task to make it clear that they had previously deleted these items, which improved the situation, but some still had problems in the second round of testing. This could be due to the fact that none of them had used Android devices, and thus were less familiar with the "Menu" hardware button.

Most users don't immediately understand the filtering functionality. Currently all of the types of activities start off selected, and the user can deselect the ones he or she is not interested in. In testing, most of the users tapped a category when they wanted to see activities from that category, and then reversed their selection once they saw the app respond. This may be due to the lack of visual fidelity of the model, since it was somewhat nonintuitive to identify which things were selected.

Once again on the topic of filtering, it took some users a couple of tasks before they realized the existence of the filters, and that they were press-able buttons. This once again may be due to low visual fidelity.

Some users were confused by the fact that in Model 1, we had both restaurants and types of food listed together. One user mentioned out loud that she couldn't tell if one listing was a restaurant name or a type of food. We changed this in prototype 2 so that only restaurants are shown, not types of food.

The delete/undelete functionality was confusing to users, especially in our first round of testing, and one user mentioned that they would never delete an item for fear they would be unable to recover it. We added an in-place undelete feature, so that any accidental deletions can be easily undone without changing to a different screen.

More about Android than our app - users who did not have Android phones had a very hard time discovering options that were in the menu activated by the hardware menu button. Android users (the target market for any Android app) had no trouble with it.

Most users (by a wide margin) preferred Model 2.

Updates to Prototype 

     

These pictures show the updated more info screens so that they show more descriptions on the first click.

...