Commentary

Stephen Wellman
 

Bye-Bye E62, We Hardly Knew You

AT&T is sending the E62 out to the smartphone retirement village. That's right, the smartphone that was destined to kill the BlackBerry is now nothing more than a memory in the minds of mobile geeks and abandoned enterprise users. What happened?

AT&T is sending the E62 out to the smartphone retirement village. That's right, the smartphone that was destined to kill the BlackBerry is now nothing more than a memory in the minds of mobile geeks and abandoned enterprise users. What happened?Alas, like so many high-tech flops, the Nokia E62 was born of compromise. The device's parent, the E61, sports built-in Wi-Fi access. But when Nokia tried to bring the E61 to the U.S., the carriers weren't quite ready for that. So Nokia stripped out the Wi-Fi and released what many mobile geeks considered an inferior device.

Nokia tried to push the E62 as the BlackBerry killer for the U.S. market, but rival smartphones, like the BlackBerry Pearl and Motorola Q, caught on with users while the E62, well, didn't.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The E61, however, has a small but devoted cult of users here in the U.S. Some insiders think the E61 could succeed as an unlocked device in the U.S. market where the E62 failed, especially as many business users look for a smartphone with usable Wi-Fi. In fact, Dell is now selling the unlocked version of the E61 on its site.

So who knows, maybe the E61 will be a hit with U.S. consumers and make up for the flop of the E62. What do you think? Are any of you dedicated E61 users?


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