Windows Mobile can't catch a break. Since the announcement of Windows Phone 7 Series at Mobile World Congress, WinMo 6.5.3 has been cast aside like an old toy on Christmas morning. The latest kick in the stomach comes from Adobe. All plans to provide Flash 10 for WinMo have been halted as the software developer targets WinPho 7 this fall.

Ed Hansberry, Contributor

February 26, 2010

1 Min Read

Windows Mobile can't catch a break. Since the announcement of Windows Phone 7 Series at Mobile World Congress, WinMo 6.5.3 has been cast aside like an old toy on Christmas morning. The latest kick in the stomach comes from Adobe. All plans to provide Flash 10 for WinMo have been halted as the software developer targets WinPho 7 this fall.I figured something like this was happening. Adobe announced support for WinMo 6.5 early last year, but here we are nearly five months after it shipped and there is no client yet. They have blamed a lack of necessary APIs in the current version of WinMo, but I am not buying that. This is a business decision straight up. From a consumer standpoint, 6.5 is dead. Microsoft may keep it around as Windows Mobile Classic to cater to some specific markets, such as Symbol for industrial customers, but it is the end of the road for consumer devices once WinPho ships, and the consumer is what Adobe caters to with Flash. I'd argue it would be foolish of them to continue developing for a platform that has been shown the door. If it really was an API issue, don't you think they'd have figured it out last year when 6.5 went gold and SDK's were published?

In addition to this info, IntoMobile is reporting that Flash for Android should be shipping this summer. As expected, the iPhone won't be getting it but that isn't a technical decision, it is a religious one. Palm's WebOS wasn't mentioned in the article, but is anyone really developing for WebOS?

About the Author(s)

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like


More Insights