Versions Compared

Key

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

...

The voting interface was implemented within the framework of the existing open source application that we branched. This framework used jamon with linked java classes to handle requests. In addition to the templates, jQueryMobile was used, which adapted html compiled in a set syntax into a nicely displayed list that scales with various mobile platforms. This ended up working very well for us and, though it took a lot of tweaking, eventually made the interaction between music database and end user more simple.

Evaluation

Users

Describe how you found your users and how representative they are of your target user population (but don't identify your users by name).

...

  • "Like" a song
  • "Like" a song, then change it back to neutral
  • "Dislike" for any offscreen song

Usability Problems

 List the usability problems you found, and discuss how you might solve them.

...

Users would have liked to see the songs re-order on the voting and playlist screens (Minor, Major respectively) The voting screen is client side scripting and could be re-ordered but would likely get confusing if ordering changed while editing. The playlist screen would simply require an event to be fired when a vote is cast and should be included.

Reflection

Discuss what you learned over the course of the iterative design process. If you did it again, what would you do differently? Focus in this part not on the specific design decisions of your project (which you already discussed in the Design section), but instead on the meta-level decisions about your design process: your risk assessments, your decisions about what features to prototype and which prototype techniques to use, and how you evaluated the results of your observations.

...