Latitude Inconsistitude

In the midst of yesterday’s I/O event, Google announced the launch of the long rumoured API for their Latitude location sharing platform; there’s ample coverage and commentary on ReadWriteWeb and on TechCrunch and that’s just fine because that’s not what I want to write about.

When it was launched in early 2009, Latitude was the receipt of some fairly harsh press from the informed tech media and from the uninformed traditional media and I argued for some latitude in the discussions on, err, Latitude.

Latitude kept on getting compared to Yahoo’s Fire Eagle and the main gripes seemed to be:

  1. Latitude is a consumer application built into Google Maps, not a platform
  2. Latitude doesn’t have an API
  3. Latitide’s privacy model is opt-in but all or nothing

So now Latitude has an API and everyone’s happy. Right?

Unofficial Google Latitude T-Shirt

Wrong. The previous gripes have been done away with and replaced with three more gripes.

  1. Latitude needs to run in the background and so will either drain battery life or won’t run in the background on an iPhone at all.
  2. Latitude now has granular privacy controls but these are on the back-end so Google will know your location prior to federating it to location consumers via the API.
  3. Latitude needs a Google account to use.

There’s a lot of inconsistency here.

  1. Latitude, as part of Google Maps, already runs in the background on handsets that support that. The iPhone doesn’t, yet, but that’s an iPhone OS issue not a Latitude issue. Short battery life is a feature of almost all smartphone class handsets, Latitude or not.
  2. Latitude gains granular privacy controls but they’re on the back-end so this is a bad thing. Fire Eagle has granular privacy controls and they’re on the back-end but this has never been a source of complaint.
  3. Latitude needs a Google account to use. Correction. Latitude has always needed a Google account to use, so this is a bad thing. Fire Eagle has always needed a Yahoo! Id to use, and yet this is something not seen as a contentious issue.

One of the criticisms that was levelled at Fire Eagle was lack of a definitive consumer application at launch; a not unfair criticism. Latitude’s taken the inverse approach, launching with a consumer application and then opening up an API almost a year later.

Time will tell which of these two location sharing platforms will dominate or whether they will be usurped by another unseen contender.

Photo Credits: moleitau on Flickr.
Written and posted from the Yahoo! London office (51.5141985, -0.1292006)

5 Comments

  • You guys were light years ahead with Fire Eagle. But as with other products the ball was dropped. Yahoo was/is good at connecting the dots early on but drops the ball. Why was this the case? Now that you are out of Yahoo would you care to pin point the problem.

    Thx!

  • and what do you think about Geo Messages approach: http://servletsuite.com/geomessage ?
    Let you share location info peer to peer and does reveal identity (actually – even does not require ID’s)

  • […] Google Latitude now has an API but it also shows some problems […]

  • @Arjun: I don’t finish my role at Yahoo! until the 28th. of May. I’ll probably be following this up with a “The Yahoo! Years” style blog post then.

  • @Den: This sounds interesting; I’ll take a look.