Towards single page applications

Here is an interesting trend:
http://twitter.com/#search?q=tennis
http://www.google.com/reader/view/#stream/feed%2Fhttp%3A%2F%2Ffeeds.feedburner.com%2Fhitwise
http://www.facebook.com/home.php?ref=home#/home.php?filter=fl_82783402532
http://mail.google.com/mail/#starred
http://www.feedly.com/home#category/Musique

As you can see in those 5 examples, some web applications are evolving towards single page applications which dynamically morph the content of the page based on the value of the hash. Various apps might have various reasons for doing so. They usually center around performance, interactivity and integration. The side effect is that the dispatching/routing logic needs to migrate from the server (apache, tomcat,etc…) to the client. This is where streets becomes very handy.

Dapper

Ran into Dapper today. Their service has come a very long way. Here is a link to their intro demo. Very cool. It would be very nice to have an extraction tool like this right into Google Spreadsheets.

Dapper

Ecosystem

Here is a photo of a whiteboard discussion we had this morning about the ecosystem in which feeddo will have to learn to live. I thought that it would be interesting to capture this so that we can look at it in 3 months and see how our understand of the environment has changed.

feeddo ecosystem

What is OpenSocial?

Introduction to OpenSocial

Google unveils their OpenSocial initiative. We have had the chance to play with OpenSocial over the last 6 weeks. In a nutshell, OpenSocial is interesting because it allows widgets and applications to asks containers (iGoogle, Orkut and others) information about you, about your contacts and your friends, in a very simple and inter-operable way. It also formalizes the concept of activity stream so that some applications can contribute events and some other applications can filter them, mash them up and display them to the user.

OpenSocial is a natural evolution of shared-authentication systems: It makes a lot of sense for each application to NOT have to have its own copy of who you are, who your contacts and friends are.

OpenSocial is also a natural evolution of personalization frameworks such as iGoogle: widgets can offer much more value to users if they have a way to learn more about you and your friends.

What does it mean for feeddo?

The biggest value for feeddo users is that it is going to simplify the task of finding the recommendation feeds of your friends. We will most likely allow you to add your most recommended feeds as a widget to iGoogle and Orkut (similar to what we do today with Facebook).

Anything else?

OpenSocial is yet another proof that JSON-driven RESTful Web Services are the right abstraction layer for exposing services on the web and that people should look at sharpening their Javascript/Actionscript skills because that is where the next wave of innovation is going to take place.

Kudos to Patrick Chanezon and the rest of the Google team for pulling this initiative off!