Commentary

RIM CEO: SurePress Ain't Going Nowhere

Most of the information we've seen about the BlackBerry Storm 2 clearly shows that the clicking SurePress screen of the original Storm is gone. Why, then, did Research In Motion's co-CEO Mike Lazaridis make a point of saying, "SurePress is here to stay"?

Most of the information we've seen about the BlackBerry Storm 2 clearly shows that the clicking SurePress screen of the original Storm is gone. Why, then, did Research In Motion's co-CEO Mike Lazaridis make a point of saying, "SurePress is here to stay"?One of the biggest (remaining) faults of the BlackBerry Storm is the SurePress screen. In order to type on the device, or make any on-screen selections, you have to physically press the screen down until it clicks. The screen is one big button. RIM calls this SurePress. Typing long missives on this device is tiresome at best, and maddening at worst.

Most were relieved to see the recent video of the BlackBerry Storm 2, which revealed that the clicking SurePress display was gone. According to the video, it appears as though the Storm 2 will simply make use of the touch screen in the same fashion that the iPhone or HTC G1 does.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Earlier this week at the D7 conference, however, RIM co-CEO Mike Lazaridis said unequivocally, "SurePress is here to stay."

He didn't clarify what that really means, though. We know for a fact that there's no click screen on the Storm 2. So are there other devices already in the pipeline that have SurePress? Has RIM re-imagined SurePress from a technological standpoint, but plans to keep the name? None of this was spelled out by Lazaridis.

I suppose all we can really so is wait and see.


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