Skip to main content

Slacker and the inspiration of small screens

Slacker is a great, genre-based internet radio application. Similar to Pandora, it delivers songs to the user in a random order (vs. on-demand listening applications like Mog and Grooveshark) and offers all sorts of customization and social networking features. In contrast to Pandora, the mobile version offers caching of music for offline listening (very cool!).

Slacker also has a strong presence in channels like IPTV, mobile, desktop and (most likely very soon, to compete with Pandora) a version for the car. However, in terms of user experience, the channels differ.

The desktop UI is clunky and cluttered with several calls to action on the main 'player' screen - they cram everything in into one view and it's not clear where to begin. Meanwhile the mobile UI is pleasant, simple and provides only the major functionality on the main screen. It is a minimalist design with very few buttons and choices for the user to make; other less-frequently used functionality is deeper in the application.

Whether this design is intentional or due to the natural constraints of a small screen, it works. Not only is the desktop design less pleasing, the inconsistency in the look and feel (across channels) makes it difficult to learn the overall Slacker model. They should strongly consider a more consistent design across channels! In addtion to simplifying the desktop UI, another improvement could be a small, simple app (similar to mobile) available from the web browser - like Pandora One.

Overall, when building music applications in different channels, designers should look first to small screens as inspiration. The simple design of mobile applications (like Slacker) can help them translate to a great user experience on a larger screen.
Update: Evolver.fm has written about a new Slacker mobile UI here...http://evolver.fm/2010/10/27/slacker-app-pandora-spotify-iphone-android-blackberry/#more-364.

Comments

Popular posts from this blog

Ultimate Guitar's many Play buttons

In any UI, calls to action must be clear - represented either by intuitively labeled buttons, or instantly recognizable icons. When they're not, your users will have to do extra work to figure out how a feature works, how to get started, how to distinguish areas of the screen. This will cause them to hesitate, be confused, and simply take more time than needed to get something done. And they'll most likely forget next time they visit your app.

In the case of Ultimate Guitar, an excellent guitar community website which includes chords (and tabs) from 1000s of songs, the detailed view of a songs's chords have too many similar calls to action.



In the image above, notice the number of tappable elements that represent 'Play'. The first and second one (top of screen) seem to do the same thing - they briefly open a different, more robust view of the tabs, followed quickly by a modal asking me to upgrade. Not only are the options redundant but only the second one has a lab…

A site map for a music application

For the past several months, I've been working with the CHIRP Radio volunteer tech team to design a mobile solution that allows station DJs to plan out their weekly shows. At a high level, a DJ should be able to browse and select songs from a massive music library, and add them to one or more playlists, which can be used for their shows. The app also has functionality like the ability to read album reviews, view recent activity by DJs in the app, and review a DJ's profile.
A site map is an important artifact when designing any application or website. It shows how the overall navigation should be structured, can be used with end users to validate the taxonomy, and is helpful for developers as a companion to wireframes or mockups.
Below is a site map I recently created for the project. The highest level navigation options are lighter in color, while as the user navigates deeper, darker colors are used to represent those options. The coloring isn't necessarily a known best p…

What made Rdio's UX so good?

On December 22, Rdio finally shut down its service, a beautiful, on-demand music streaming application, which didn’t do anything extraordinary when it came to functionality - they had discovery, sharing, playlist management, and a mobile offering just like their competitors. But it was the user experience that set it apart from others like Spotify and Apple Music. Simple, organized, intuitive, and mobile-first.

Clean, simple UI - Screen density is often an issue with music apps trying to cram every piece of recommended content and social function on the screen at once. Rdio's beautiful, simple design (with plenty of white space and good use of color and typography) makes for a clean interface so users don't get overwhelmed with all of the options and content being shown at any given time. Users notice important things like calls to action since they stand out so well.

Well-organized - Things are where you expect, including a small set of persistent navigation options on the left…