Commentary

Microsoft Attempts To Explain Its Windows Mobile Naming Conventions

When Microsoft launched Windows Mobile 6 back in February, it also renamed the different versions of the software. Now, rather than actually describing what specific device they're for, the names are vague and confusing: Standard, Professional, and Classic. Find out why.

When Microsoft launched Windows Mobile 6 back in February, it also renamed the different versions of the software. Now, rather than actually describing what specific device they're for, the names are vague and confusing: Standard, Professional, and Classic. Find out why.Apparently the whole thing sprung from the fact that no one knows what a smartphone really is. (Is this a difficult concept to grasp?)

Ed Hardy over at Brighthand recently dug up a blog entry from Windows Mobile Team developer Mike Calligaro. In it, Calligaro attempts to explain why the different Microsoft Windows Mobile 6 products' names were changed. You can read the whole exchange here. The end result is this:


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

* "Windows Mobile Professional" is for the touchscreen devices (i.e., Palm Treo 750); * "Windows Mobile Standard" is for non-touchscreen models (i.e., HTC 3125); * "Windows Mobile Classic" is for traditional handhelds with touchscreens but lacking cellular-wireless capabilities (i.e., Dell Axim).

Rather than be descriptive about what type of device the versions are compatible with, though, the new names feel more like selections you'd make based on your income or work status.

Does anyone every choose to use software or hardware deemed "classic" (i.e., old, for fuddy-duddies, no longer hip)?

My grandfather's '57 Chevy is classic. "Stairway to Heaven" is a classic. While it's totally cool to cruise in a classic '57 Chevy listening to classic rock, I am not sure how many people are going to try out "classic" software. Is this Microsoft's way of saying, "Put that hardware to pasture and upgrade"?


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