Skip to main content

The pain of transferring songs from iTunes to a Kindle Fire

Since the Kindle Fire uses the Android platform and all of my music is located on a Mac/iTunes using iTunes Match, I expected there to be a small challenge transferring songs to the Fire but I Google'd 'transferring songs to a Kindle Fire', found an overview of the process on Amazon and seemed like the steps would be fairly simple. However, the overall workflow was cumbersome and confusing.

I read the instructions and (after logging into Amazon) followed a link to the Amazon Cloud home.  I quickly noticed a clear call to action - an 'Upload Files' button in TWO locations on the screen and it was a well-organized screen (although it wasn't clear what Lists was, on the left side).  And uploading files seemed fairly intuitive and flexible by 1) control-clicking the file and choosing 'Upload to Cloud Drive', 2) dragging them to a Cloud Drive icon in the menu bar or 3) clicking the Upload Files button which invoked the native Mac folder window where I could select files or folders.  3 easy ways! 

Now I just had to upload those Shins and Katy Perry songs so my daughter could use them on her Fire.  I uploaded 24 songs and saw them on the Cloud Drive screen but…

I had uploaded 24 songs under the wrong amazon account (mine, not our other family account).  Now what?  I logged out of Amazon and logged back in under the correct account and discovered a message on the top left of the Cloud Drive screen that read 'Want to upload or download your music? Launch Cloud Player'.  I didn't notice this before since the two 'Upload Files' buttons caught my attention so fast.  I clicked it of course since all I wanted to do was upload music. Then something called the Amazon Music Importer, a totally different looking screen, opened in another tab - now I was confused.  Which way was I supposed to upload music? Using Cloud Drive or Music Importer (both Amazon products!)?

The Cloud Drive screen said I had 5GB of total storage (with no reference to music) available but the Music Importer screen (actually branded as Amazon Cloud Player) said I could only upload 250 songs, way less than 5GB.  And one was based on total storage and the other based on number of songs.  Later, I noticed the Cloud Drive screen actually did reference music (an Archived Music folder in the main table).  Amazon needs to present clear options to upload files to the cloud.  On the landing page for Amazon Cloud, they should state clearly that one product is meant for music and the other for non-music files. Apple does this pretty well in marketing iTunes Match.

I guess I'll go through the work to upload the songs now via Cloud Player since I have to upload those music files to the Fire but, even with all of iTunes Match's shortcomings (latency, missing artwork, review to come), I found Amazon's varying file upload products to be a confusing experience. Based on first impressions, the process of uploading songs is more intuitive and simply seems to 'just work' a bit better using iTunes than Amazon's Cloud product.


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…