Commentary

Ed Hansberry
 

Microsoft Ran Out Of Time On Windows Mobile 6.5 UI

During TechED, Microsoft admitted that the Windows Mobile 6.5 was rushed a bit and will ship without all of the intended features according to a report by Gizmodo. This is not too surprising since 6.5 seemed to come out of nowhere as a stop-gap measure since WinMo 7 was too far out.

During TechED, Microsoft admitted that the Windows Mobile 6.5 was rushed a bit and will ship without all of the intended features according to a report by Gizmodo. This is not too surprising since 6.5 seemed to come out of nowhere as a stop-gap measure since WinMo 7 was too far out.Loke Uei Tan is a senior project manager at MS for Windows Mobile and during a conference panel about Windows Mobile, uttered these words:

The reason why we couldn't complete the interface on Windows Mobile 6.5 is because of time. We only spend what, eight months, nine months, to build 6.5 from ground up and it's actually an amazing engineering feat. But, in order to do that, we had to do some prioritization and we had to cut certain features. Eventually, we will make sure that the UI capabilities are carried out throughout the whole platform.

More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Rumors about Windows Mobile 7 have been swirling for at least two years and has been seen as the OS to get the mobile platform more competitive with consumers. Thanks to the iPhone, Windows Mobile is seen as relatively user unfriendly. The iPhone showed what a real mobile browser should look like and for most of the world, removed the need for a geeky looking stylus forever. WinMo 6.1, the currently released version, still requires a stylus for its touch screen devices to hit the small icons and app controls or to easily navigate the menus.

By now you've seen images of WinMo 6.5 with the honeycomb interface and large menus designed for pudgy fingers. It is clear the iPhone has been a major source of, uhm, lets call it inspiration, for the platform. But by Microsoft's own admission, this isn't where they want to be. They just ran out of time.

In fairness to Microsoft, they continue to have to deal with something that Apple hasn't with the iPhone, and that is an existing large userbase and thousands of applications. When the iPhone came out in 2007, they had no compatibility issues to worry about with applications or drivers. In fact, they didn't even support native apps on the ordinal device. It didn't matter what the UI was, it wouldn't break anything. Microsoft deals with this all of the time on the desktop side. Compatibility issues were probably the biggest reason people avoided Vista. Windows Mobile has sold tens of millions of devices in recent years and there are thousands of applications and peripherals. With each new version of WinMo, some of those apps and drivers get broken, but MS goes to great lengths to maintain compatibility. Those efforts though slow down the pace of innovation, and it really shows in WinMo 6.1. Even though the iPhone is about to hit 3.0 this summer, the basic UI hasn't changed in two years, they have just added more features.

It still is frustrating for users though that have invested resources into Windows Mobile to have to wait. 6.5 will give some relief, but 7.0 is what we are really waiting for and that is over a year away. We already know the upgrade story on 6.5 - some 6.1 devices will be upgradable to the new platform, but it is up to your carrier to provide it, something they seldom do. If you buy a 6.5 device, will it be upgradable to 7? Perhaps, but chances are slim, as they always seem to be.


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