On the state of location networking

Location-networking is meant to provide two experiences:

1. Broadcast your location to your friends and FoaF network in the hope of making unexpected connections; and

2. Share comments and rich media (photographs, video, voice etc.) about your experiences at a particular location.

This then, is the state of my location networking experience one year on:

state-of-social-networking

Two problems have remained stubbornly unresolved for that entire period

1. The lack of two-way sync between Brightkite and Fire Eagle – While I can understand why Google Latitude won’t play with Fire Eagle, I’m puzzled by the reluctance of the other players in location networking like Brightkite and Foursquare to integrate with Fire Eagle. Integrating with Fire Eagle would allow location-networking providers to stop worrying about how their users send updates to their service and focus on making the experience more fun to use. Instead, all the players in location-networking are guilty of listening only to the echo-chamber hype of early adopters and providing solutions only for the platforms the geeks love, i.e., the iPhone, the Blackberry Bold generation and the Android OS. This is remarkably short-sighted considering:

a. While the iPhone is the fastest selling Smartphone today, it still isn’t beating older Blackberries, Windows Mobile or the Palm OS in terms of installed base.

b. No Smartphone is coming close to beating the "dumb" cell phones install base

If location-networking is to really become as ubiquitous as social networking, it has to run on a variety of platforms and require little by way of a hardware minimum. The promise of location-networking, to open your phone and see the location of not just your friends but of your FoaF network is truly remarkable. But meeting only the needs of the echo-chamber will keep location-networking a niche product, until it is killed off by the geeks who abandon it for the next cool thing on the horizon.

2.  The lack of rich metadata for any media shared through Brightkite – Let’s ignore the fact that Brightkite does not support video uploads to Flickr (despite the fact that Flickr has had  video in place for over a year now). No, my complaint is about how little metadata is passed to Flickr when I send a photo to Brightkite.

a. No tags

b. No Titles

c. Email subject as description

c. No EXIF data

Using the Email Subject line as a description isn’t a very great idea either – why can’t we specify the Title via Email Subject and the description via Email Body? Isn’t that more logical. The lack of tags means these images are going to be very hard to surface via search. All in all, it’s a very limited and clunky solution for something a lot of other products do very well.

I had hoped that 2009 would be the year that location-networking really started to take off. It now seems like location-networking will continue to stagnate until someone builds a product that not only works for the early adopters, but for the early majority and the users after that

This entry was posted on Tuesday, August 18th, 2009 at 3:48 pm and is filed under Geek. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Comments so far

  1. [Blog] On the state of location-networking http://is.gd/2msdf

    This comment was originally posted on Twitter

  2. I am a bit confused here. You are saying that in various ways, brightkite sucks. But then you say that because of suckage like this, location based networking is still niche. Are you using brightkite as an example in that all services suck similarly or am i misreading your conclusions? I don’t follow this category so no idea which it is.

  3. antrix – Brightkite is the largest location-networking site out there so it’s a poster child for the kind of suckage that I’m talking about. But Google Latitude and foursquare are equally guilty of this sort of problem. I’m not aware of any other location-networking sites at the moment.

Have your say

Note: This post is over 6 months old. You may want to check later in this blog to see if there is new information relevant to your comment.

Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.