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.

Snippets from CTIA's "A Generation Unplugged" keynote

Harris Interactive presented the “A Generation Unplugged” study results at a keynote session at CTIA yesterday. For the survey Harris Interactive surveyed 2,089 teens ages 13-19 about their motivations, usage and behaviors towards mobile phones.

Harris hinted at making the presentation available for a price, so I thought I would post the following highlights:

• About half of teens interviewed say they would die without their mobile phone and ability to make calls. Texting was not far behind.

• The two biggest motivators of mobile usage for teens are: 1) staying in touch, and 2) (surprise) feeling safe

• Mobile gaming is not so important to teenagers. Self expression is much more important

• Status is first established by the clothes teens wear, and secondly by the phones they own

• What the phone does is more important than the way it looks

• Teens love ring tones, but they like texting and picture messaging, and more than surfing the web

• Teens like small phones but with a lot of features

• Teens text more than they talk on the phone

• Teens like text because they like that it allows them to multitask, that it's fast, easy, and cheap

• Loyalty for teens is driven by relevance of features, phone diversity, customization - in order of importance.

• Teens want to own multiple devices

• Most teens purchase at carrier brick and mortar
  

• Teens are most influenced by parents, then their friends, then their boyfriend or girlfriend, and last by celebrity endorsements

• When it comes to Games, teens want better selection, experience, and controls. However, overall teens care less about gaming than communication when it comes to mobile

• One in three teens browse the mobile web. Top apps are email and social networking. However, most social networking is taking place on the PC

• The biggest barrier to adoption of mobile video is cost

• Teens don't mind ads on mobile device

• The dream phone: water proof, endless power, scratch proof...

• Teens want from phones: emergency transmitter, translations, 3D, remote control, TV (in order of preference)

• "The phone of the future" according to teens: flexible material, just software, paper thin, appended to your eyes, wearable, projector screen

• Teens want a single device for all or their consumer electronics needs
  

• Teens dislike location applications, but they want GPS

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).

>play's "Beyond Mobile 2.0"

I attended the UC Berkeley Digital Media and Entertainment >play Conference this past Saturday. The mobile panel focused around a somewhat vague, yet interesting topic: “Beyond Mobile 2.0”. The panel consisted of Steve Lee, Product Manager at Google Mobile, Tico Ballagas from Nokia, Jeff Sellinger, VP of Mobile at CBS, Rick Robinson, VP Products and Services at XOHM/Sprint, Evan Tana, Director of Product Marketing at Loopt, and moderated by Mike Rowehl of Sillicon Valley’s Mobile Monday, and AdMob’s tech dude. Some of the predominant themes were:

Location:

The most heard theme was: LBS is the key to providing targeted content.

According to Rick Robinson, the biggest problem with adoption today is the lack of privacy. However, I would agree with Evan’s response that the privacy control tools are in place today, so the biggest challenge is education (of consumers about these controls).

On Future of paid on deck applications:

According to Steve and Evan, both Google and Loopt get the whole ‘playing with carriers’ deal today, but believe the market is slowly moving to a more open environment. Nokia truly believes this, which was clear by Tico’s constant reminder that Nokia is evolving into a services company. Proof of this is the company’s launch of Ovi and late acquisitions (Navteq, Enpocket, Twango, and Loudeye). Rick Robinson from Xohm went as far as saying that "Xohm will tear down this wall..." (BIG statement!), but will still provide an on-deck expericence that is customized for the device.

Interoperability of different technologies:

The best description of what a rich end user experience might be was Jeff Sellinger’s. This would call for an interactive behavior between the different applications that exist on the mobile device. Jeff said it would be great to be able to tie SMS/MMS with WAP and Location. I would add streaming video and interactive gaming to this fabulous equation.

Limitations in the U.S.:

* Limited MMS support by U.S. carriers was the top item

* Absence of unlimited data plans, as in Europe, was mentioned repeatedly as a roadblock for user adoption

* Pervasive broadband (both availability and adoption) was mentioned a few times as an issue
Device fragmentation, specifically with browsers, was also mentioned as "old" but never ending "news"

Google Navigator

I pay $4.99 per month for Verizon Wireless's VZNavigator. VZNavigator is a Brew based LBS applications that gives turn by turn directions, local directories, maps. VZNavigator has gotten me out of many a hairy situation. The past few times I have used the application, however, I get a sporadic error telling me it is unnable to retrieve the directions I have requested.

When this happened to me today, I decided to try Google's SMS directions. I sent "directions from (my work address) to (graphing social paterns conference address)" to the short code 46645 (GOOGL). Within 30 seconds I received three messages including the turn by turn directions. So while I didn't have a friendly voice dictating to me where to turn, nor access to a map, I was able to get to my destination just fine. I must admit it is pretty tempting to want to save myself $5/month going forward... Especially when it takes almost the same amount of time and effort to type the directions request onto the SMS message, than to navigate through the device's convoluted menus to get to VZNavigator.

Off-Carrier LBS platform

Hats off to the folks over at Yahoo! Research Berkeley for developing something truly disruptive!

The Yahoo! Research Berkeley team has come up with an open LBS platform that allows the community to generate and openly obtain the location information. This is in contrast to other LBS platforms, most of which are owned by carriers.

“Fire Eagle”, code name for YRB’s open LBS platform, allows location-based applications to connect to it and 1) post end-users’ location information, and/or 2) get end-users’ location information. Here is an example of how it works: Suppose you, as a developer, come up with the “Totally Rad” Social Networking location-based application and connect to “Fire Eagle” using its soon to be made public API. Now, let’s say one of your users also uses Zone Tag. While out and about, this user takes a picture, tags it, and uploads it to Zone Tag. Zone Tag will determine the user’s location by means of its Cell Site ID database. Zone Tag will then post the user’s location information to the “Fire Eagle” platform. Next, the end-user will log in to the Totally Rad Social Networking application. The Totally Rad application will get the user’s location information from Fire Eagle. With this information Totally Rad will be able to serve your end-users with location information about their friends or love interests, or even highly targeted ads.

So what about the security of users’ privacy?

Privacy has always been the number one concern with location-based services and continues to be. YRB promises the platform will be armed with privacy features. First, the location history of users will not be maintained. Fire Eagle will only cache each user’s latest posted location information. Second, users will be able to manage through a Web UI which applications should or should not have access to their location information. I would add to that the ability to specify windows of time, ability to turn off the disclosure on information from the device, etc.

How good will the information be?

Unlike a carrier supported LBS application, a user’s Latitude and Longitude may not always be available.

What might the carriers say/do?

They may not do anything until a user’s location information is compromised and used in a bad way… or until they see that this significantly eats into their revenues. For now, though, this is probably will be just noise to them.

What’s Fire Eagle’s status?

Currently “Fire Eagle” is about to go through alpha testing. Enter your email address on the Fire Eagle Website to be notified when it becomes open to the public.