very interesting read, +1 to you sir.
I'm interested to see how this develops. This could just be the thing to restore confidence in the windows mobile computing space. Of course its going to take another year or so for it to pick up steam.
No caveats now: Windows Phone 7 is a waste of time and money. It's a platform that no carrier, device maker, developer, or user should bother with. Microsoft should kill it before it ships and admit that it's out of the mobile game for good. It is supposed to ship around Christmas 2010, but anyone who gets one will prefer a lump of coal. I really mean that.
The bottom line is this: Windows Phone 7 is a pale imitation of the 2007-era iPhone.
The developers at Mobile Beat quickly recognized the labor-intensity of this UI method and one asked the Microsoft rep if anyone had bothered to test it with users. The answer was essentially "no" -- a scary thought indeed.
Inexcusably old technology limits Windows Phone 7But under the hood, Windows Phone 7 gets worse. The core problem is its backward set of technologies, which will fundamentally limit IT, developers, and users alike. Here are some of the more egregious examples of Windows Phone 7's time warp: * Its browser is Internet Explorer 7, with some IE8 capabilities added -- that means it does not support HTML5, as the iPhone, Android, WebOS, and Nokia Symbian all do. Didn't anyone on the Windows Phone 7 team know about IE9 and its embrace of HTML5? Why isn't Windows Phone 7 using IE9? * It does not support multitasking except for Microsoft's own first-party apps, meaning the browser, email client, SMS client, and other such preinstalled applications. When you switch applications, they shut down -- just like the iPhone did until iOS 4 was released this spring. Android and WebOS, of course, supported multitasking more than a year ago, and Google and Palm mercilessly attacked Apple for not supporting it as well. Yet Microsoft didn't build multitasking into Windows Phone 7 at the outset? * This lack of multitasking also means there's no such concept as interapplication communication for third-party apps, not even for a primitive work-around such as the iPhone OS 3.2's "Open In" feature. Thus, apps can't work together à la in WebOS -- even though the UI that Microsoft has shown off seemed designed to do just that. The only thing that Windows Phone 7 will do is let third-party apps call first-party apps, so clicking a URL in a text message will launch the first-party IE browser to show the URL. Of course, doing so closes the app that had the text link in it. (First-party apps can call other first-party apps, and these would all continue to run in parallel.) * It doesn't support copy and paste. Here again Apple was a much-criticized laggard, supporting the capability only in summer 2009. Microsoft says it didn't have time to get this feature in for the first release (!) but will have it in a future version. Too bad there's not likely to be a future for it. And how could Microsoft not have copy and paste working in Windows Phone 7? After all, it had copy and paste in Windows Mobile 6.1.
I'm still shocked that Microsoft isn't showing any smarts or competitiveness behind its mobile OS. When the iPhone first came out, a wait-and-see attitude made sense. But more than three years later, it's crystal-clear that the iPhone is no fluke and that it has in fact redefined the mobile market. During this sea change, what has Microsoft done? It wasted a couple years screwing around with Windows Mobile 6.5. When everyone ignored that faux effort, Microsoft made a lot of noise around Windows Phone 7 yet also diverted resources to an array of mobile OSes -- seemingly as insurance policies against Windows Phone 7's failure. Windows Phone 7 should have been Microsoft's "man on the moon" project, but now it's clear that the Windows Phone 7 was Redmond's equivalent of the bungled Hurricane Katrina response effort.