Storagebod Rotating Header Image

Not a Cloud Post!

Currently I have a whole bunch of blog posts half-written but at the moment inspiration seems to have gone a bit south. So I thought I would post on something completely different although it'll probably mutate into something familiar.

Now anyone who watches my twitter feed will probably have seen a few tweets on Spotify, the streaming music service available in some countries in Europe and coming soon I believe to the States. Although not the only streaming service available; it is in my opinion one of the best, it has a great selection of music covering all genres (I recently discovered that it has a growing classical selection) and it has great clients available for Mac and Windows but no Linux at the moment.

It also has two great mobile clients, one for Android and one for iPhone. If you want to use the mobile client, you must pay for the premium service but if you are happy with your music being interupted by adverts every now and then, the desktop version is free.

Now Spotify and services like it in many ways embody what to me is the real beauty of the Cloud model; a service which can be accessed anywhere from many devices but at the end of the day, the end product is the same, music streamed to my ears.

But this post isn't about Cloud, it came about after a brief MSN chat with a good friend of mine who specialises in all things Web 2.0 and especially getting useful information from the Internet; he's been training librarians and all kinds of other people how to use the Internet for years. And he mentioned that he had recently given a talk on how things like Spotify change things; it breaks the link between the physical instantention of the artifact and moves it completely into a virtual world and in doing so, it changes certain value assumptions.

Spotify for example has millions of tracks, now they are all searchable and I can just search for an artist and play their content; certainly, that's often how I use it but it also has the concept of playlists and publically shareable play-lists and it is these which will become more and more treasured and valuable.

Of course, it would be really useful if I could take Spotify playlist and then point it at another service such as Sky Songs and if playlists were portable. Or even take my iTunes database and point that at Spotify. I guess what we are talking about is portable metadata formats or at least gateways between services, in the Cloud or perhaps just stored locally.

Oh heck, this was a Cloud post anyway! We need to ensure that when we are building services or consuming services that in order to truly leverage the power of the Cloud, that we think about portability and flexiliblity. My playlists are currently locked into Spotify (and iTunes) but I am actively thinking about how I get round this and build a truly portable store; we need to think about this in our work lives as well.


One Comment

  1. Adrock says:

    Isn’t that what M3U is for? If we want true portability, we need to use open standards. Take your Spotify example. Why the need to Mac and Windows clients? Shouldn’t it just run in a browser, thereby being compatible (well, mostly) with any O/S?
    As for Cloud, The Cloud suppliers seem happy enough to give us all their APIs for free. But I wouldn’t even say there is a race between all them to become the defacto API, most of them are simply developing something it in-house and hoping for the best. Maybe Simple Cloud API or some equivalent will catch on, or maybe one vendor will simply outdue the rest and become the defacto standard (like how SCSI caught on.) But I think you are right and the flexibility especially needs to be implemented for those compute services out there.

Leave a Reply

Your email address will not be published. Required fields are marked *