Commentary

Google's Latitude For iPhone Is A FAIL On Many Levels

The Web burst into excitement yesterday when Google made its Latitude location-sharing service available for the iPhone. That excitement was short-lived, however, once users discovered the the "application" is limited to the iPhone's browser and isn't a stand-alone application at all. Turns out even the mighty Google will bow before Apple's demands.

The Web burst into excitement yesterday when Google made its Latitude location-sharing service available for the iPhone. That excitement was short-lived, however, once users discovered the the "application" is limited to the iPhone's browser and isn't a stand-alone application at all. Turns out even the mighty Google will bow before Apple's demands.First, a little bit about Latitude itself. It can be found in the iPhone's Safari browser at google.com/latitude. The service allows users to sign in and share their location with a set group of friends. Everyone needs to opt-in to share and see location information. Latitude lets you see a list of all your contacts who have already signed up for Latitude, and allows you to add them easily to your list of Latitude contacts. In my tests of it, it wasn't not nearly as accurate as the iPhone's GPS can be. Actual location results were typically off by a mile (pun intended).

From my perspective, something like this would be most useful when you're trying to coordinate a meeting between a bunch of friends or colleagues who are spread out in the same city. I can picture a scenario in which I'd use Latitude at a trade show to see where everyone is around town. The problem is, there are serious limitations with Latitude on the iPhone (not including how terrible the accuracy is).


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I think this admission by Google spells it out pretty clearly:

We worked closely with Apple to bring Latitude to the iPhone in a way Apple thought would be best for iPhone users. After we developed a Latitude application for the iPhone, Apple requested we release Latitude as a web application in order to avoid confusion with Maps on the iPhone, which uses Google to serve maps tiles.
I have one word in response: LAME.

Users have to open the browser and leave it running in order to use Latitude. That means it won't work in the background. This feature should be incorporated directly into the Maps application on the Phone, which, by the way, uses Google's Mapping data. That makes much more sense, and would give it a better chance of actually providing accurate location data.

Google even admits this. It said:

Unfortunately, since there is no mechanism for applications to run in the background on iPhone (which applies to browser-based web apps as well), we're not able to provide continuous background location updates in the same way that we can for Latitude users on Android, Blackberry, Symbian and Window Mobile. Nevertheless, your location is updated every time you fire up the app and then continuously updated while the app is running in the foreground.
To me, that's a direct pot-shot at Apple and a weak attempt by Google to appease users (like pretty much everyone) who might be disappointed with the way Latitude works on the iPhone.

In this case, Google and Apple both fail.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links