It's not about Location... duh!

If I had a dollar for every time someone mentioned foursquare during a panel or keynote at SXSWi last week I would be super... Ok, maybe I'd have about 60 dollars. Which is a lot considering I only attended about 6 sessions in all (bah... and missed out on the "panel nerd" badge as a result... whaa!).

The point is that Foursquare's debut at SXSWi was simply put, a success. We all loved it and continue to love it!

The irony is that it is about the millionth LBS application to see the light of day. Worse yet, many of the check-ins were likely done over SMS given AT&T's stellar performance during the conference. Worse yet... it is a resurrection of Dodgeball.

The reality is that the majority of Foursquare's new fan base has tried many of its precursors (from the mobile operators' friend finders, to Loopt, to Dodgeball, to Brightkite). This explains how easily we adopted it - Yes, we got it. But the thing is that not only did we start using it right away without the need for a step by step explanation of why and how to use it, but we also could not stop ourselves. This never happened with any of Foursquare's predecesors.

So at last someone seems to have finally gotten it right.

First it's fun -

Foursquare is unique in that it turns the potentially cumbersome task of providing your location into something you actually want to, cannot wait to do. Why? Because it is a game! And as with games you earn points, you compete, you win prizes (badges), you get to PWN your friends by becoming "the mayor" of a bar. Next thing you know you can't stop yourself. Next thing you know you catch yourself having horrible dark thoughts about checking into a place you're not even at!

Second, it's useful -

Much like what Yelp, Rateitall, or Google Maps could do, foursquare gives you location based recommendations. The beauty of these recommendations from a contextual and cost perspectives is that they have been provided by the user community. What is even more beautiful is that from a monetization perspective this could be a very valuable capability. For years companies like Cellfire have been toiling with this concept. But again, what was missing was the fun part.

Back in September I summarized this teen survey which concluded with the very astonishing revelation that (gasp! OMG) generation-m did not care for friend-finder applications. I guess we'll just have to see if they change their mind once they PLAY foursquare.

My Location: Google is Not Always Watching Me over the Airwaves

Google surprised us again this week with yet another bold announcement. With My Location Mobile Maps will be able to tell you where you are. But fear not, big-brother or stalker phoebes. In contrast to Google’s free WiFi service, Mobile Maps has made the very intelligent decision to not bother to know where you are. All My Location knows is an arbitrary identification number (not your MDN, which is your seven digit phone number) that is associated with your mobile device.

The challenge for operators is that whether their LBS platforms provide anonymity or not, it will be difficult for them to shake off the perception that they do not. The network knows the MDN associated with the device; the MDN is associated with the account. The account not only holds information about the identity of the subscriber, but even other facts such as mailing address and credit card number.

Google’s announcement also sparked new discussions about how the carriers ought to release LBS APIs that application developers can take advantage of. This only speaks for the U.S. operators’ inability to effectively educate the media. After all, as I have posted before, some operators do have open (or semi-open, depending on whether economics are part of the definition) APIs. So here is a quick snapshot of carrier supported LBS APIs for developers:

Verizon Wireless
Sprint
ATT

Right now Mobile Maps is limited to smart devices such as Blackberry, Windows Mobile, and Symbian. However, in America it is feature phones that occupy the largest footprint today. So why doesn’t Google take advantage of the semi-open API’s provided by operators? Hmm… perhaps they will soon… Or perhaps the economics get a little murky since operators impose revenue share models on subscriptions to on-deck applications. To make things even more complicated, with Brew operators a third party is also involved: Qualcomm. In contrast, Google’s model is based on advertising, which means giving the service away for free. So perhaps with a little creativity, and suppression of egos, all players could come to friendly terms that would ultimately benefit us, the end users.

Regardless of how this will pan out, the truth is Google’s is definitely a good long term strategy; eventually most, if not all, devices will be open smart devices.

I end this post with the real question that I have: will Google make Mobile Maps open like its online counterpart some day?

(Here is a good interview with the Google Maps product manager, Steve Lee).