Skip to main content

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 label 'interactive tab'.

The third, a play icon, only displays when I tap the Audio button and plays the song via an integration with Apple Music (super useful!). But the identical play icon below that (the fourth) does something totally different than the third - it scrolls the page slowly helping the user play along with the tabs. As the audio controls (for playing the song) collapse, the user sees only one pause button, on the same row as the Audio icon, which makes it unclear what the visible play/pause control relates to (is it for scrolling? for playing the song?).

A couple of suggestions would make the screen more usable...
  • On the top, remove both of the play buttons, and convert the 'Interactive Tab' text to a button, top right giving the user only one clearly labeled play option. This will also remove some clutter, making the screen less dense, letting the user focus on what's important. 
  • On the bottom, consider using the same gray background (used for the active Audio button), for its related play/pause controls in the above row, leaving the scrolling controls white. The slight variation in color across rows will help users distinguish the one set of controls from the other while the gray color will establish a visual relationship between the Audio button and its controls.





Comments

Popular posts from this blog

Buying gear on Reverb

A couple of weeks ago, I wanted to buy an inexpensive stand for my acoustic guitar. I was already familiar with Reverb, which is an online marketplace to buy and sell music gear. Without knowing much at all about guitar stands, I did a search, landed on their site, and within several minutes I was able to research and purchase a new stand. From the helpful information about different stands to the last step of the checkout process, the user experience was great

After Googling 'guitar stand Reverb', one of the first results was a super helpful article on Reverb titled, 'The 6 Best Guitar Stands for Every Budget'. It listed all with all of the comparative specs I needed right on the page (saved me from having to look at each stand's page). Knowing my budget was small, I selected the On-Stage XCG4 Classic Guitar Stand. The price was right, the design was simple, and reviews were good. There's only one I caught that could be improved - when I curiously tried a sim…

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…