Location-based services offer amazing future possibilities. Restaurants can offer just-in-time discounts to people nearby fill empty tables. Similarly, People can pick a restaurant where their friends are currently enjoying “Happy Hour”. Stores can offer targeted coupons to browsing customers based on their buying habits. Meanwhile, I can find a nearby store that has that hot Christmas gift in stock while I am shopping.
The success of companies like FourSquare demonstrates the potential of these possibilities. However, right now early adopters are the primary users of location-based services. Many mainstream consumers refuse to use them. Why? Because they do not trust location-based services (yet).
Why many still fear location-based services
What is the cause of this mistrust? Fear of losing control of offline privacy. Most of us now accept that information they post to the Internet could likely be publicly available (how much Generation Y cares about this vs. the Baby Boomer generation is an entirely different debate).
This fear and mistrust will only increase as many new players enter the location-based services market. Some will only use your location services when you explicitly approve this; others will “store your approval” using your information without explicit notice (you can see this already in many location-based apps). Some will carefully protect it; others will have data breaches that disclose months of data on what you were doing, when, and where. Some will even sell your data to third parties (perhaps not initially, but when new sources of revenue are needed, after “notifying you of changes to their Terms of Service”). The consequences of these disclosures on privacy are enormous.
A simple way to address these fears
There are many ways to address these fears: industry (or legal) standards for use of location information, creation of registry of trusted location-based applications, etc. However, these means of protection are complicated (wherever there is complexity, there are many sources for unexpected outcomes). They also require consumers to trust location-based service providers to do the right thing, without error.
There is a well-known precedent for this: the silent/vibrate button. When mobile phone came out, people needed to make them silent when they went into meetings, movies and restaurants. Those mobile phones that made this simple were loved; those who didn’t were not. The love of the physical toggle switch reared its head again a few months ago when Apple removed the ability to lock iPad rotation with it’s physical switch (they restored the feature after much uproar in the next point-release).
This is NOT a placebo
I know, many of you are saying this is a simple placebo. Mobile phones already broadcast your location to your telecomm provider. However, the sharing and management of this location information is different than that used by location-based service application. It is not broadcast over the Internet (“Jim just check-in to…”); it is only attainable via search warrant or similar legal procedure. In addition, it is approximate (Verizon knows my location, plus or minus X meters; I do not positively confirm which store I am in); location-based app data is tagged with metadata that makes it much more exploitable.
Instead it will let location-based services “Cross the Chasm”
Putting a location services on/off toggle switch into the next major release of smartphones will make it far less scary for mainstream consumers to adopt location-based service. Having this physically in smartphones will create infrastructure from which application developers and consumers will all benefit. The first mobile provider who does this will definitely gain an advantage, especially if it does so in partnership with an App Store-delivered application provider. Will it happen first on Android (due to its openness) or it will happen first on iOS (as part of Apple’s holistic user experience)? Or will Nokia’s sufficiently influence Microsoft to provide this (Finland is known for its strong privacy protection)?