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.

Comments

Popular posts from this blog

Setting a price alert on Stubhub

A few weeks ago, my wife and I really wanted to see Alvvays and Frankie Rose at Metro in Chicago. But the show sold out and I was left to look for tickets second-hand. I've used Stubhub before to purchase concert tickets but up until now, hadn't tried their Price Alert feature which lets you set a ticket price max and be notified when the price goes below it. The user experience from beginning to end was really good. The feature is easy to find and provides very mobile-friendly controls to create the alert. The Price Alert tab was prominent on the event details screen - very easy to find. Note: today (1/5/18), Stubhub has removed those tabs and you have to tap an Info button top right of the viewport to look for the same feature. It's a still a good UX once you get there but it's an additional step. The Price Alert feature is intuitive and uses tappable numbers to let me pick the quantity of tickets (not a clunky dropdown menu or less efficient plus/minus p

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

KEXP's new Apple TV experience

I love KEXP . It’s a listener-supported radio station in Seattle. It streams all around the world on its website and mobile app. And they’ve had a really good app for the Apple TV for some time - great to stream in the house at a high volume!  And I’ve reviewed them before here . Oh, and also here .  They recently released an excellent new version of the app for Apple TV. And although it doesn’t introduce a lot of new features, it’s way more visually engaging and maximizes the screen real estate much better than before. Here are some of the major changes... Additional, prominent functionality- Archive (stream any show from the past) and streaming Settings The old version had a lot of wasted, unused screen real estate while the new version makes more efficient use of the screen New, large, colorful tiles along the bottom represent each song played in chronological order You can scroll left and right to see history of songs played (much further back in history than before) Larger album