...
- 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.
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.
Usability problems discovered from testing:
- MAJOR: Learnability, Efficiency - Users almost all found the task: "Setting a thumbnail the collection thumbnail" difficult to do. The thumbnail was not editable from the Collection Properties page, which was where most users first looked to execute the task. Though long pressing is a normal thing in applications, users did not find long-pressing an obvious feature of our application. There is no feedback that suggests that a long-press does something (in other applications that we looked at, most long-presses cause vibration or something).
- MINOR: Efficiency -- Users generally did not find naming an item a necessity, which made the collection view page unaesthetically pleasing because it was cluttered with Untitled1s. We can solve this by making removing the name labels from Collection View.
User tests:
Briefing: Reading briefing. Tested Portrait mode, landscape mode behavior is unspecified.
...