Commentary

Wireless Operators Raking In Your Cash With LBS Apps

Location-based services accounted for 51 percent of wireless operator mobile content revenue for the second quarter of 2007. Seems GPS-enabled handsets paired with navigation and other services are catching on.

Location-based services accounted for 51 percent of wireless operator mobile content revenue for the second quarter of 2007. Seems GPS-enabled handsets paired with navigation and other services are catching on.The stats (from Telephia) are slightly misleading, but impressive all the same. About 13 million people downloaded a mobile application on their phone in the US in the second quarter. While the LBS apps represented 51 percent of revenue, they were not 51 percent of the number of downloads. LBS apps are pricer than most other apps, averaging a hefty $9.23 per download, versus $3.82-$5.41 for weather applications, sports, wallpapers, and pictures.

That so many people are willing to pay nearly $10 for a get-me-from-here-to-there type application is telling. "With consumer awareness increasing, there is enormous potential for even greater LBS growth, especially since Telephia research indicates that there are approximately 130 million GPS-capable handsets in the US alone, and growing," said Doug Antone, president and CEO of Networks In Motion.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Some other interesting data came from the research. About 7 to 13 percent of mobile users download content such as games, wallpapers and ringtones. Only 5 percent, though, have downloaded an application such as an LBS-based navigation service.

As popular as LBS services are, based on those numbers it looks like the wireless operators need to convince more people to download and use mobile content.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links