Spotify Mobile – Google I/O in San Francisco
So I just returned from an awesome week in San Francisco where Anders, Ludvig and I demoed the first version of Spotify mobile on the HTC Magic Android device. We’ve worked very hard on this application for the last few weeks and are pretty pleased with the result. Using it on the trans-atlantic flight was a good test of the offline sync mode, really useful! 😀
I really like the HTC Magic (thanks for giving everyone a free device Google), it’s pretty clear that the form factor is everything when you compare it to the G1. It actually makes my iPhone feel just a little bit big…..
Spotify for Android at Google I/O
The event itself was huge fun. The party on the Wednesday was in true Google style with any and every geek interest represented + ofcourse, the sign of Google, lots of free food and drinks!
I probably don’t need to mention the Google Wave presentation to anyone, how can you have missed it? I would like to say however, that I think the general blogosphere has kind of missed the core of what it is (which is easily done, considering it took 1,5 hours just to demo all the different things it CAN do). But in one sentence, Google wave is about Centralized conversation objects, where everyone edits the same object, rather than the current distributed model, where everyone has local copies of conversations and edits (replies etc) to their individual copy. This basic paradigm difference allows for all of the rest of the features (realtime, simultaneous update, in message editing, collaboration etc). I actually think they should’ve stuck to just the core messaging use case for the demo, to not confuse it too much.
It’s a super ambitious project in itself, but what really blew me away was the fact that they are going after a federated solution right away (i.e. I can have my own Google Wave server), meaning there will be multiple copies of these conversation objects, that need to be kept in sync. I think it was crucial that they did, it just wouldn’t have worked to say that all future communication should be hosted by Google themselvers, but it does make it orders of magnitude more complex I would guess…..
