Tag: api

Scenic Tours

To start off the Picasa-Maps mashups, I’ve put together an example that combines a Picasa photo album feed with the Map API’s recently announced Driving Directions feature to calculate a driving route that will get you a similar set of photos. Now, no need to be jealous of your friends’ pretty landscape albums – just copy them! Try it out below by clicking “Load Album & Route.”

with a bit of additional hacking, a youtube version of this shouldn’t be too hard.

Facebook Platform

Metaphorically, Facebook is providing the ease and user attraction of MySpace-style embedding, coupled with the kind of integration you see with Firefox extensions, with the added rocket fuel of automated viral distribution to a huge number of potential users, and the prospect of keeping 100% of any revenue your application can generate.

facebook makes the sharecropper life so convenient

Facebook App Anatomy

Below you will see all these various components as they are applied to our own Photos Application. It should be noted that none of these pages are mandatory but the more you include in your application the richer the experience becomes (for example, no one’s going to install your app called “Lefty” that is only a left nav link)

kudos for allowing such deep integration.

Uniform Google API

I’ve been reading the Google Data APIs blog for a few months and have been impressed at how Google has been quietly executing on the plan of having a single uniform RESTful Web service interface to their various services. Contrast this with the API efforts on Yahoo! Developer Network or Windows Live Dev which are an inconsistent glop of incompatible RESTful protocols, SOAP APIs and XML-RPC methods all under the same roof. In the Google case, an app that can read and write data to Blogger can also do so to Google Calendar or Picasa Web Albums with minimal changes. This is not the case when using APIs provided by 2 Yahoo! services (e.g. Flickr and del.icio.us) or 2 Windows Live services (e.g. Live Search and Windows Live Spaces) which use completely different protocols, object models and authentication mechanisms even though provided by the same vendor.