In the past 2 years, the industry has finally moved beyond LBS as a category to LBS as a feature. As stated previously, “What app wouldn’t be more useful with location?”! What’s misunderstood in all of this is how location is retrieved by the app and what this means.
E911 (government mandated subscriber location lookup) in the early days was the initial motivation for opeartors to introduce network-based location lookup. This location is acquired through a combination of network triangulation technologies and is delivered to the requested entity (eg person or app) via a positioning server. This approach is often referred to PDE or carrier-based location lookup.
The challenge with PDE has been in business models; operators have been charging for PDE location queries and a variety of middle-men and/or aggregators have been trying to sell this access (eg Wavemarket, Autodesk’s former mobility group, Alcatel Lucent and others). Most developers obviously can’t afford to pay 5-10 cents per location lookup and have thus resorted to the many free alterantive ways to get location such as determining location by the cell tower or getting location through WiFi or most obvious, getting location from GPS (readily available through APIs in smartphones today.
You may ask, why PDE if you can get location in other means? The challenge with the alternative solutions, is that the app can only get location for you (and you only). This is great for use cases like Google Maps but what if you wanted to get the location of your buddy or what if you wanted to send an SMS when one of your friends walked by your house – yes, that would be kind of creepy but advertisers love this scenario (proximity marketing). Unfortunately, the only way besides doing a FourSquare check-in to get the location of one of your buddies or a passerby is using carrier-based location lookup.
To entice more developers, many of the carrier location aggregators have been trying to offset the 5-10 cents per query pricing via alternative business models. For example, a developer can receive subsidized queries in exchange for sharing advertising revenue from their app. Unfortunately as much as mobile advertising is growing, it still cannot offset even a 5 cent query. The better question to ask is why is there a charge at all – if PDE was free, there would be a whole new set of apps that could be enabled built leveraging real-time location. For example, without needing an app running in the background, I could track the entire life-path of a user – an advertiser’s goldmine in terms or profiling! Well, as with most things, the reasons things are the way they are is often not the most logical:
1. Without naming operators, some can’t scale PDE. I’m pretty sure they want to open it up, assuming the right privacy features were in place but the query volume would kill the network infrastructure. Let’s see what happens as initiatives like GSMA’s OneAPI continues to push forward – this is a solvable problem.
2. Some operators are restricted by their licensors. For example, CDMA operators use Qualcomm’s QPoint to power the PDE and likely have licensing fees based on volume that inhibit their capability to open it up.
3. And of course the biggest problem is that there are a handful of developers (eg Family Locators) who are actually paying 5-10 cents per query. Unfortunately, when somebody is willing to pay, then let them pay even if it inhibits innovation. I guess we’ll have to wait for Google to make it free (somehow)!
In any case, let’s see how this evolves. Carrier-based location lookup can open-up a whole slew of new applications that cannot be achieved effectively today. It moves the problem from getting location to the larger problem of privacy which many others are trying to tackle.
Follow This Blog Via Email
- SXSW 2016: Messaging Bots
- Reflecting on the Productivity Category
- Tech Discrimination
- Daily Active Users Don’t Matter!
- IOT: The Competition for Attention
- How Google and Others Are Using Data Science to Speed Up Productivity
- Why I’m Excited About Google Glass?
- Context Is a Layer and Not a Category
- Sales 2.0: The Bottoms-Up Sales Model
- Is UX Going to be Commoditized Next?
- To Win Enterprise, Target the Consumer
- Using a Chromebook for a Week
- Android (and the Tab!) in the Enterprise
- Ad Learnings from Recipe Search
- CPA Advertising on Mobile
- Enterprise Mobile Is Hot!
- Network Responsibility
- In-Door Mapping
- The Social Network
- Using a Mobile Phone to Drive Behavior Change
- Apps vs. Web Apps
- Understanding Developer Psychology
- Are Batteries Improving?
- Over the Air and Emerging Markets
- Are Platform Game Lobbies the Next Social Graph?
- Are Plugins (and Flash) Going Away?
- Lessons Learned in Monetization
- Understanding the Emerging Market
- OEMs, Please Choose
- Understanding PDE (Positional Determining Entity)
- Has the Power Shifted Back to Operators?
- Is the Killer App the App Store?
- Navigating the Mobile Content Landscape
- Wholesale Application Community
- Sharing Overload?
- The Ad Ballot
- Device Patent Wars
- Is Apple Making a Mobile Wallet Play?
- Top 6 Reasons Why Nokia Doesn’t Have a Capacitive Touch Screen
- Mobile Trends 2020
- Mobile Taking a Cue From the Travel Industry
- CTIA Party Analysis
- Measuring AT&Ts Network
- Mobile Cloud Computing
- Mobile Beyond & NARIP
- Mobile 2.0 Advertising Notes
- Carnival of the Mobilists #193
- The Broken Subscription Model
- The Mobile Reserve
- The Fragmented Web
- Got to Love the Music Industry
- What Platforms Should I Build For?
- To Operator or to Not to Operator
- What Do Bankers Do?
- My Older Posts