Light Reading Mobile – Telecom News, Analysis, Events, and Research

Light Reading's 2012 Mobile Life Survey is full of small surprises, especially since most of the survey respondents make their living in the telecom business.

I tried to see if iPhone users in our survey were likely to own a Long Term Evolution (LTE) device already or if they had plans to buy one soon.

Nearly 80 percent of the folks who say they are iPhone users (they identified their smartphone OS as Apple's iOS) do not currently own an LTE device.

About 68 percent of that same group (iPhone owners who own no LTE devices now) say they have no plans to purchase an LTE-powered device this year.

Android users, the other big group of mobile users in our survey, weren't all that different. Seventy-four percent of the Android users we surveyed say they do not own an LTE-powered device.

About 66 percent of the Android users that took our survey and do not currently own an LTE device say they have no plans to purchase an LTE-powered device this year.

For some reason I thought the Android users would have a stronger intent to purchase something LTE-related. I'm not sure why I thought that, but they weren't that much more likely to buy anything LTE as the iPhone users we surveyed.

So, most folks surveyed who aren't LTE device owners aren't looking to change that in the near future. What could the industry do to change that? Should those intentions be viewed as pessimistic, or should we assume that these numbers mean nothing but upside for LTE device makers?

— Phil Harvey, Editor-in-Chief, Light Reading

Most folks have no intent to buy an LTE-powered device this year. What might change their minds?
March 21, 2012 | Phil Harvey |


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

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing 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. Network Computing 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.
 
Related Videos
White Papers SPONSORED CONTENT
Featured