Versions Compared

Key

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

...

Design 3

Storyboard

Analysis

The learnability of this interface should be easy because this interface borrows from many other commonly used interfaces.  It uses the stage setting to display the list of streams in the center of the screen in both the search view and the category view.  The playlist also copies from the Grooveshark interface, where the "album art" is shown horizontally in the playlist.  The learnability of this interface might be hindered by the ..............xxxxxxxxxxxxxxxxxxxxxxx

The visibility of this interface is very large and open.  The playlist is always in view, so you can know what is coming up next and what previous streams you have seen before.  When viewing search results, the main part of the interface comes up with the results in a list view, providing easy viewing of the results.  

The efficiency of the interface is not the best, but is also not bad.  The limitations in the interface are that it is a mostly mouse driven interface and everything must be searched for.  There are no visual indicators of relevance to the user for what they are searching for, other than the default ones of play/pause/etc.  In later revisions, there could be the possibility to navigate with the keyboard, but this would still not increase efficiency very much, as the user would still need to search.  The efficiency comes from consistency in the interface, having the central location being the list of streams viewable, with the playlist at the bottom.  

The errors in this interface should be very recoverable.  There will usually be one button on the interface that returns to the previous screen they were viewing.  They will also be able to use the back button to return to a previous screen.  The user might make an error just out of making a mistake, or missing the click target, but it should not be very faulty.