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?

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.

Another Piece Of Bloggage By Gary

Self professed "geek with a life", geo-blogger, geo-talker and geo-tweeter, Gary works in London and Berlin as Director of the Places Registry for Nokia; he's a co-founder of WhereCamp EU, the chair of w3gconf and sits on the W3C POI Working Group and the UK Location User Group. A contributor to the Mapstraction mapping API, Gary speaks and presents at a wide range of conferences and events including Where 2.0, State of the Map, AGI GeoCommunity, Geo-Loco, Social-Loco, GeoMob, the BCS GeoSpatial SG and LocBiz. Writing as regularly as possible on location, place, maps and other facets of geography, Gary blogs at www.vicchi.org and tweets as @vicchi.

Mail | Web | Twitter | Facebook | LinkedIn | Google+ | More Posts (271)

Other bloggage that may or may not be geo-related to this one:

1. Latitude Media Coverage Needs More Latitude

   A product launch from Google is accompanied by a massive media campaign that reaches far beyond the techy demographic; Google is a consumer brand these days and their messaging generates...

2. Facebook Places; Haven’t We Been Here Before?

   A week and a half ago Facebook finally launched their Places feature to a predictable media furore over location privacy, regardless of whether it’s justified or not and, to location...

3. Location Privacy Issue? I See No Location Privacy Issue

   Telematics, the use of GPS and mobile technology within the automotive business, and the Web 2.0, neo and paleo aspects of location have traditionally carved parallel paths, always looking at...

4. More Location Tracking; This Time From Foursquare

   Back in March of this year I wrote about deliberately tracking my journey by using Google’s Latitude and unexpectedly tracking the same journey by looking at the history of my...

5. Deliberately (and Unexpectedly) Tracking My Journey

   I’ve been tracking my journey and in doing so inadvertently uncovered a sea change in the way in which we view the whole thorny issue of location tracking. Yesterday, Ed...