Commentary

Microsoft Fights Back Against WinMo 6.5 'Unfinished' Claims

Some Microsoft folks recently posted a video about Windows Mobile 6.5. The main message that appeared to leak out was that the user interface was rushed and incomplete. In response to the negative headlines, Microsoft posted another video in an attempt to do some damage control.
Some Microsoft folks recently posted a video about Windows Mobile 6.5. The main message that appeared to leak out was that the user interface was rushed and incomplete. In response to the negative headlines, Microsoft posted another video in an attempt to do some damage control.Just yesterday, my colleague Ed Hansberry reported on the original video. He quotes some of the language used by Microsoft senior project manager at MS for Windows Mobile, Loke Uei Tan. In Tan's 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.
Turns out, that's not the message Microsoft wants everyone to be focusing on. In the new video, Dale Coffing and Chris DeHerrera take us through a number of the new features and user interface improvements that have been cooked into Window Mobile 6.5. The main message? Windows Mobile 6.5 is complete. Other things seen in the video include a nice demonstration of the new Internet Explorer 6 and the as-yet-unreleased MyPhone service.

Check it out here or here.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


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