Versions Compared

Key

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

...

  • A primary design decision we made was to ground the app around user-contributed images, that is, pictures and thumbnails they take and provide of products that they own. This decision, we found, was effective in that it gave users flexibility as to how they wanted specific items organized, and gave users their own mental model of what the images actually were.
  • Simplicity was a key feature of our prototype -- we received positive feedback from all levels of testing that the simplicity of our user interface made it much easier to use. We were initially afraid that the interface would be too simple in that it would effect learnability; however, a reduced layout actually contributed to learnability and efficiency.

GUI Section

ScreenShot

Design

Implementation

 

Image Added

Users are first greeted by our home page, which is a simple layout of buttons. Relative button size corresponds with frequency of use -- that is, the larger buttons are more frequently used than the smaller ones. This data was found from user polling and testing.

...


 

 

Image Added 
Image Added
  Image Added

We opted to make collection view laid out with images and with names of the item underneath it. Initially we toyed around with text or image only, but we found during our testing that users responded best when both were available. Clicking the menu button brought up a bottom menu. Long-pressing on an item in the collection would bring up a more detailed menu; however, we found this to be among the most difficult menu for users to find (more detailed in evaluation).

 

 

 

 

 

  •  
  •  
    Image Removed  Image Removed  Image Removed
  • A simple, non-obtrusive item adding layout was most effective for our purposes. We feared, initially, that users would find it not revealing enough and would have understanding problems; however, users seemed to pick up fairly quickly on how to add items to their collections.
  • Adding a new collection has a similar unobstructive interface. This also adds for consistency across our application.
  • To share a collection, we enter the sharing menu and input the name and editing privileges. This sharing menu was one of our most difficult design decisions, and the current iteration of it is thanks to input from paper and computer prototyping. Our previous design decisions were too complicated, and we found this current one simple and easy for users to use.
  • Searching for items in our application is as simple as clicking on filter and typing.

...

  • We chose to implement this software on Android because the picture taking functionality translated best on a mobile application. We utilized the Android SDK, coding primarily in Java. The frontend was handled with Android's own XML view layer. The backend was handled with SQLite databases.
  • In general, we followed a Model-View-Controller pattern, where the ContentProvider and SQLite abstracted the database information into data models, the XML layer contained the View, and the bulk of the Java code was the controller.
  • One major implementation problem we encountered was simply lack of familiarity with the platform. None of our team members had ever programmed in Android before, and found the learning curve sufficiently steep enough to be problematic
  • Each item was represented as its own model. Collections contained an expanding list of items. Items could have as many tags as necessary.
  •  

Evaluation

  • In general, we found that users found the application easy to use and navigate. Users enjoyed the simplicity of the application and the ability to do the same task through multiple, but natural, avenues.
  • The users we chose were representative of our population in that we chose users from different age ranges, who also generally found the need to organize large amounts of items.

...

  • Brief users with following brief:
    Panel

    Collector’s Catalogue allows users to view and organize their collections on the go. By tagging and taking pictures of items, users can keep track of and search their large collections through visual recognition, without having to recall solely from memory.

    Remember that we are testing the application, not you. Feel free to explore, and think your actions out aloud. If you find yourself confused, or wishing for something extra, let us know, and again, feel free to comment out loud with any observations you make.

    This session should be fun, so relax and make yourself comfortable. If at any time you want to stop, you are free to do so. Thank you for taking the time to help us user test the application.

  • Ask users to preform following tasks:
    Panel

    1)      Create a new collection, and add some items with photos and tags.
    2)      Share your new collection with a friend for viewing.
    3)      Starting from the Home screen, quickly search for a crab.
    4)      Delete the “imaginary” animal item, since it doesn’t belong.
    5)      You decide you need some help managing your board games, so you share the collection with a friend, and let them co-manage it with you.
    6)      Go back to the collection you created, and set one of your items to be the collection thumbnail.
    7)      From the Home screen, make a new board game item and add it to the app.
    8)      Finally, you’ve decided that you have too many shoes, so you want to delete your entire shoe collection

Briefing: Reading briefing. Tested Portrait mode, landscape mode behavior is unspecified.

...