Commentary

Ed Hansberry
 

Windows Mobile Update Story Gets Better

Like any mobile platform, Windows Mobile has its strengths and weaknesses. One of the weakest areas is the upgrade story, or rather, the lack of much of a story at all. I can just about count on one hand the number of devices graced with an upgrade from one WinMo version to another, but that will be changing with WinMo 7.

Like any mobile platform, Windows Mobile has its strengths and weaknesses. One of the weakest areas is the upgrade story, or rather, the lack of much of a story at all. I can just about count on one hand the number of devices graced with an upgrade from one WinMo version to another, but that will be changing with WinMo 7.I Started Something had a discussion with Loke Uie Tan, a technical program manager for Windows Mobile and the update story has been confirmed. It originally surfaced back in April when Microsoft posted a job description that mentioned the update.

Currently, users are at the mercy of their carrier or OEM to release an upgrade. Even if the phone manufacturer does issue an upgrade, like HTC, that is no guarantee the cellular company will offer it. This is even when the upgrade is free. For example, when the WinMo 5 devices started shipping in 2005, they lacked the ability to use the new push email feature that Exchange 2003 SP2 had. Instead it relied on the old method of waiting for the server to send an SMS to the device to wake it up and initiate a sync. Microsoft offered the update for free in the hopes that all WinMo 5 users would get the upgrade, but they didn't. I know first hand T-Mobile didn't bother releasing an update for their brand new SDA.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I guess that even if the update was free, the testing, deployment and subsequent support in the event of a problem aren't free. The upgrade scenario from one version to the next is worse because it isn't just a minor update but an entirely new OS and Microsoft doesn't give those away for free.

In the future, this will be changing. From the article:

Recognizing the current barriers with the process of upgrading Windows phones today, it can be confirmed that the Windows Mobile team are indeed working towards modifying the system architecture to potentially enable delivery of OS updates without affecting and/or requiring the phone ROM - effectively cutting out the OEMs, telcos that currently and unnecessary slow down the update cycle.

This will mirror what happens on the desktop. Buy your computer from whomever you want but when Microsoft releases an update or upgrade, you can apply it at your discretion. Apple has been doing this since the iPhone launched and Android and WebOS also have this model.

This won't happen tomorrow though. I suspect this change requires substantial modification in how the OS is built and would be something that makes more sense to include in WinMo 7 than in WinMo 6.5, which still shares be basic underpinnings of the other WinMo 6.x family.

WinMo 7 should be out in 2010, so we don't have too much longer to wait for this. It is good to see Microsoft is pushing back against the carriers on this and taking matters into their own hands. The carrier's attitude has basically been that you got what you paid for when you purchased the device and there are no promises of upgrades. That might work with a $50 feature phone but not with a smartphone. The carriers don't get that a smartphone is a computer and people expect upgrades.


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