Commentary

Stephen Wellman
 

Are Mobile Devices Suited For Exploration?

This week CIOs and senior IT managers are heading off to the Gartner Wireless & Mobile Summit to learn if their businesses can afford to pony up for a new mobile deployment.

This week CIOs and senior IT managers are heading off to the Gartner Wireless & Mobile Summit to learn if their businesses can afford to pony up for a new mobile deployment.Before the summit, Gartner analysts Dale Kutnick and Ken Dulaney sat down to discuss some of the themes they will address at this year's event. During their discussion, Dulaney argued that mobile devices aren't yet ready for exploration, i.e. the kind of tasks where an employee goes out to actively search and learn something new. Dulaney argued that desktop Web browsers are perfect for exploration, but due to their small screen sizes and limted form factors, cell phones and smartphones were only good for serial tasks, such as sending and receiving e-mails and text messages and following small data alerts.

I'm not so sure I agree with Dulaney. I think the time is fast-approaching when smartphones will enable mobile workers to complete both serial and exploratory tasks from the field. Even now, I can use a Treo pretty effectively to perform some simple search tasks, edit any number of documents, and even browse the Web for fun. Mobile browsers have come a long way in the last three years, especially on smartphones like the Treo or some Symbian and Windows devices.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Surfing on non-smartphone handsets is still a chore, but it's getting better. Even new handsets without touchscreens, like the Motorola Q, are remarkably easier to surf with than their non-touch screen predecessors of a year ago.

What do you think? Is Dulaney right? Are smartphones and cell phones only good for e-mail? Or do your employees successfully use their mobile devices to perform more complex tasks?


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