Commentary

Stephen Wellman
 

Are Dual Mode Smartphones Really Overhyped?

Some analysts and industry insiders have claimed that dual mode devices are overhyped. I share their skepticism about new technologies and I agree that we need to caution against hype. But, I have to ask a question: Doesn't the iPhone prove that dual mode access is ready for primetime?

Some analysts and industry insiders have claimed that dual mode devices are overhyped. I share their skepticism about new technologies and I agree that we need to caution against hype. But, I have to ask a question: Doesn't the iPhone prove that dual mode access is ready for primetime?Dual mode technology has been around for a while now -- it's almost four years old at this point. The real impediment to dual mode smartphones and other mobile devices has not been the technology. The road block has been the carriers.

The success of the iPhone has proven that dual mode devices are ready. As I blogged last month, the iPhone demonstrates that dual mode access is no longer kludgy. Try using the iPhone on a Wi-Fi connection. If that experience doesn't prove just how cool dual mode can be, then nothing will.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Heck, even RIM is preparing to launch a dual mode BlackBerry. I think that's a sign that the business market is ready. And based on a recent panel I moderated, I can tell you that many many IT managers are eager for dual mode smartphones.

What do you think? Is dual mode access still just hype? Or is it ready for primetime?


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