That article seemed incredibly long for something that failed to tell me even a single thing about the phone, aside from it "looking great" or something. Come on.
Though in a way, it almost doesn't matter. Microsoft has to offer the features of iPhone and Android to even be taken seriously, so we have to assume that is just there. What they really need can't be seen through promising text and screenshots, anyway: they really need polish.
Microsoft has been notoriously bad about leaving all kinds of holes in their products, so that they look OK on stage but end up feeling clunky as hell. If they are to have a chance this time, it is important that their phones feel simple and logical; and, dare I say it, they should even be a joy to use. Microsoft will never earn my respect until they can prove that they get this, and deliver it.
Neither Google nor Apple have offered many of these people what they want in a dev environment. Apple's required an odd language up until very recently, and even the C# language you can write to doesn't do many of the things they're used to doing C# in.
Android's development resources are capable, but Eclipse is a far cry from Visual Studio...
I assume tons of people will flock to the Win7 Phones unless they are just horrible once they get going.
Many game companies can target this platform much more easily than the iPhone/Android handsets as it also works off XNA.
Many game companies can target this platform much more easily than the iPhone/Android handsets as it also works off XNA.
Seems like its lack of OpenGL offsets that a good bit... yes, a lot of Xbox/Windows games will be easy to port, but it seems like more ports will likely to be coming from iPhone/Android.
Following up to myself here: this could have some interesting benefits for Microsoft, too — iPhone has the most/best games right now, but Android is selling a ton of units so lots of folks are thinking about porting their iPhone games to Android. If WP7 was the inverse of what it is (if it had OpenGL and no XNA), it'd be seen as the third platform, something to maybe, possibly consider porting to once you'd ported to Android. That doesn't seem desirable at all. At least with XNA, they'll have the possibility of getting a lot of different games than what is available on iPhone and Android... some differentiation, which is exactly what they need.
The tools don't matter, it might be nice, but even though "tons of people prefer the Microsoft environment" I can't recall the last time they produced a product having superior user experience thanks to those tools. I can't name a single website/webapp/desktop app that I enjoy using on a daily base made with visual studio. I know a lot of the game companies use visual studio (c++) to produce parts of their games, but I'm not sure which of the latest games are produced using XNA.
My point is the tools don't matter as much as the strategy and decisions of Microsoft in other parts of the ecosystem to attract talent to produce content for their devices.
But it's a correct one. Razzle is used internally for building the kernel and drivers, but the majority (I believe?) of the userspace is done using VS.
Sorry, totally disagree. Tools matter. A LOT. Being able to build my LOB app in VB and launch on a company's phones = huge win for IT Departments.
The world isn't all about consumers and flash. Whether or not they can win that market is an open question, but they'll make a dent. And Blackberry has built a very successful business doing just that (doing ok with consumers and crushing enterprise)
Not only is this article poorly written, but all of the subsequent TechCrunch articles suck as well. As Homer Simpson once said, "You take forever to say nothing."
I think it's fantastic. As someone who has done a decent bit of iPhone development, I can definitely say that I prefer developing in VS with C# than XCode with Objective-C.
It's disheartening that so many bloggers are dismissing this awesome platform simply because Microsoft is "late to the game", yet they forget how successful Android has been. At this point, it looks like Google and Microsoft are fresh and new, whereas Apple is trying to prolong the life of an old platform.
While I might agree that the Obj-C language is long in the tooth, iOS/Cocoa Touch is really a new platform that sprung from the ashes of the aging Cocoa.
The iOS folks got to start from near scratch, building on the foundation they already knew so well.
> It's disheartening that so many bloggers are dismissing this awesome platform simply because Microsoft is "late to the game", yet they forget how successful Android has been.
Not only that, but I recall dismissing Xbox because Microsoft was so late to the game for video-game consoles that I thought they couldn't possibly have any impact.
I think the fear for Windows being "late to the game" isn't that MS will have a hard time getting mindshare, but I think they are going to have a hard time getting "developer share".
Basically if I'm going to develop my hip new mobile app that's ready to take over the world I'm going to start with Android and iPhone and wait and see what OS I'm going to tackle next, and the way I'm going to figure that out is by sales numbers and right now even there are more Palm devices then WP7.
>I think the fear for Windows being "late to the game" isn't that MS will have a hard time getting mindshare, but I think they are going to have a hard time getting "developer share".
Microsoft already have huge developer mindshare. All they have to do is get developers that already use their platforms to use yet another of their platforms.
This is especially true since you develop for WP7 on proven and well-known technologies (.Net-ish, C#, XNA). A great many developers are already intimately familiar with these and will have little or no barrier of entry with WP7.
Hmm.. I should have been more clear. My, not very well put, point wasn't with respect to developers available. Its allocation of developer resources. If I'm going to develop a mobile application I'm going to start with the platforms with the greatest reach.
I am unable to locate any hard numbers for the adoption rates of Silverlight (there doesn't appear to be any officially published figures), but something tells me it's a lot less then the 41.7 million 360's sold.
I think that you're right that both are "successful." But I believe I'm not alone in thinking that the 360 was a far greater success.
edit: Further research shows 56% of browsers for September sport Silver light (http://www.statowl.com/custom_ria_market_penetration.php), but this is hard to compare apples to apples. Personally, to me a ~$300 purchase is worth a lot more then a free plug-in download anyway in terms of how successful something is.
What follows is entirely opinion and based on little-to-no research, so if I'm way off I apologize:
I'm not sure I would classify Silverlight as "successful", just yet. Certainly it's getting buy-in in corporate environments, intranet apps, etc., it's visibility to the public still seems pretty small. Certainly there have been claims made (which I have no reason to doubt) that Silverlight has an install base of > 50% of the PCs on the internet, but I just don't see it having nearly the same "mindshare" as Flash or even HTML5. Now, this may all be a symptom of spending my browsing time on sites like HN and Reddit which are, if not anti-Microsoft, certainly not pro-Microsoft, so take this all with a grain of salt.
Amongst .NET developers Silverlight definitely seems to be popular -- I just don't know what portion of the overall developer population consists of .NET devs. As someone who spends a certain number of hours each day actually working on Silverlight-based stuff, I can say I like Silverlight, and it's the right tool for the job we're using it for.
After some reflection, I'm not sure what I would constitute as "success" in this space, to begin with. Is it driving a big video site like YouTube? I big gaming portal like Kongregate? I'm not sure those are great criteria for evaluating success, so perhaps my initial evaluation is off.
When I say Silverlight is "successful" I mean that it has gained a reasonable installation base (> 50%) in a short period of time (3 years).
In early 2009, Silverlight's installation base was only 20%, so it's clearly making inroads.
Will Silverlight ever get Flash-like install numbers? I doubt it, but I also don't think it needs to have those numbers in order to be considered successful.
If Microsoft could get the kind of adoption rates for WP7 as it has for Silverlight, I think they would be very pleased. Of course, phones are a little more difficult because it's much more likely to be a binary decision - people can have Flash AND Silverlight at no cost; I doubt there will be many people interested in owning an iPhone / Android phone PLUS a Windows phone.
It's become way too common to see people slagging on Microsoft gear without providing any kind of detail, so I'm just going to start asking them for some kind of backing data.
Now, if the OP had said "is this the next Xbox, or is it the next Kin?", then I probably wouldn't have had anything to say about the matter.
Yeah, I think the problem for Silverlight is that "success" is not a clear idea for such a platform, and if "success" is just large sites using it, then you've got Netflix at least. I'm sure Adobe counts "success" as installed base, but if you were a marketer, the kicking they are getting from the development community is not success at all.
It seems more cut and dried in the phone space. Sell units, make happy customers, sell more units. Android is not necessarily making numbers 2 and 3. We'll see when iPhone hits Verizon.
It's not you, the developer, that's important. The customers buying the phones are.
Regular people already know about Android / iPhone. There are already cheap Android phones on sale (you can buy an unlocked Android phone, with no contract, for $300 ... see HTC Wildfire).
And many people are buying these phones for the apps available. For consumers the iPhone is king. Android is playing catch-up (but it is doing OK).
And speaking about regular people, my wife owns a WinMo 6.5 phone that will not see an official upgrade to 7 because it doesn't have the right hardware. And all apps for WinMo 6.x will have to suffer complete rewrites. So all the developers working on WinMo 6.x apps have just been fucked.
> At this point, it looks like Google and Microsoft are fresh and new, whereas Apple is trying to prolong the life of an old platform.
That's new to me, considering the iPhone 4 is still the best smartphone out there.
I'm currently working on several applications for WP7. The development experience for WP7 is a million-billion times better than it was for past Windows Mobile operating systems.
- The emulator is snappy and you don't need to mess around with ActiveSync.
- I'm not a huge fan of the XAML (the Silverlight/WPF markup language), but that is not an issue. I put a XAML place holder element in place and add controls in C#
- The built in controls look great and are surprisingly functional. I specifically thinking of the Panorama control - which allows application content to basically flow off screen. Some may find that style of having content get cut off by the edge of the display off-putting, but its effective if that truncated content is limited to titles.
- putting XNA in there is great, mostly for familiarity's sake. You still have to design for the phone differences (form factor, input, and library). Porting games over from XBox live probably won't require an enormous app-rewrite. Can't wait to see how this particular piece plays out.
The one drawback I can see has to do with Windows Phone store. I'm not really sure what the story is there. Is app distribution really limited to the store? How about enterprise apps?
I don't have experience developing iPhone or Android apps, so I won't comment on whether or not WP7 is better in that department.
My limited number of contacts at MS tell me that an Enterprise deployment solution is coming, but they couldn't get it done in time for the initial release.
It's improved with IOS4 as you can now deploy wirelessly by having the users visit a web site. With 3 the only way to deploy was using the configuration utility or have the users install with iTunes.
What we keep begging them for is the ability to point out users at our own enterprise app store, hosted on either Apple's servers or our own. It's also what I keep telling MS whenever I get a chance.
It's impossible to distribute an iPhone or an itouch as the user interface to custom hardware. It's also impossible to distribute an internal application if you only have 499 employees.
Big differences. MS is betting big on this, whereas with Kin it was a small team that did it. Kin apparently had very little internal support. Kin wasn't pushed by MS, but had a contractual obligation with Verizon. That's why Kin launched on one carrier only. Apparently WP7 is launching on 60 carriers, with 9 or 10 different phones. The mobile, VS, Silverlight, XBox, Zune, and Office teams are all apparently very engaged.
MS won't kill this. I wouldn't let that be a factor on doing development. Now it may take a while for it to get consumer uptake. That may temper if you want to develop for it. But given that this device should sell moderately well with a good app store, it may have better ROI than the same app showing up in the Android app store, even with the larger number of Android devices.
Apple doesn't need competition to motivate them. They've shown that by reinventing the iPod every year even though there's no competition to speak of. If anything, Apple is obsessive about innovating.
I am a big fan of the UI. Snappy and minimalist. I know that Windows Phone has music enabled in the background through the hub api for apps like Pandora and Slacker, etc. All it needs is Copy/Paste (early 2011) and reasonable multitasking capabilities atleast for certain apps. I think the most use of Multi tasking for me on the iPhone right now is to toggle certain settings or to do certain stuff during navigation. I don't really use it beyond that and it's reasonable that most of the multitasking is done this way.
I've also played around with the Google Nexus One and the HTC Incredible. While they're great phones in their own right, the touch screen experience leaves a lot to be desired (atleast on those units) in terms of response time and accuracy + the camera on nexus one is nowhere near the iphone 3GS, forget iPhone 4.
Disclaimer: I have been using the iPhone since the past 3 years and currently on the iPhone 4. I think it's time that I tried a new platform because I'm simply bored of how the phone looks and how it operates (launch an app, exit an app, etc. for everything). I like the way multitasking is implemented and how well the camera performs. I've always had the craving for a hardware keyboard and it seems like the new Dell phone with WP7 is a good replacement for my phone, probably early next year.
I've heard WP7 has no compatibility whatsoever (so it's unable to run even WM5/6 apps)? If that's true — am I understanding properly that MS is introducing almost completely empty platform, which requires software to be written yet?
I don't know whenever they will succeed or not, but it seems to be a hard task to enter the market when all rivals already have quite strong positions (including lots of software).
If anything I think that's the move they needed most - to toss everything out and start new.
See for example: OS9 vs. OSX
The problem with MS, constantly, is that they have prioritized backwards compatibility over just about everything else - often usability, stability, and functionality. This has kept their platforms technologically backwards and their usability an infamous joke.
It's about time that MS started fresh with a modern, relevant platform. I just hope they can do something similar with desktop Windows.
I'd love to see it happen, but it's not looking great at this point, at least for the near future. It's entirely possible that the Midori project is continuing behind closed doors, but Singularity (the kernel and base runtime) has entirely stagnated from what I've seen. Since they're already working with an open source (if not Free) base, I wonder if they won't just pick up one of the pure-managed OS projects out there and use that (e.g. Cosmos, Renraku, SharpOS, etc).
Disclosure: I'm the project lead for Renraku, so I have a bit of a vested interest in seeing that happen.
I think that's the move they needed most - to toss everything out and start new.
I wholeheartedly agree, and from everything that I've seen of WP7, I'm impressed. MS has rethought the entire UI, and frankly, rebuilding from scratch was the only thing they could do to become relevant again in the consumer mobile space. They've done away with the desktop metaphor, menu bars and contextual menus, and yet they managed not to make it a carbon copy of iOS or WebOS. I can't wait to test it.
However, just a side note about your comparison between OS9>OSX and WM6>WP7: whenever there was a radical change in architecture, Apple provided a transition period where the two coexisted. When Apple switched from 68k processors to PowerPC, developers could build FAT Binaries that would run on both platforms. When Apple switched from MacOS 9 to OS X, MacOS 9 apps could still run within the Classic environment. When Apple switched from PowerPC to Intel processors, PowerPC applications could still be run within a layer called Rosetta.
Re backwards compat... I think MS did the right thing here making the applications have to be managed. The WP7 managed stack seems really well-tuned (especially for a mobile device).
Removing native code from 3rd party apps gives them several things:
1) Reduces incidence of memory leaks.
2) Less buggy apps w/ better type safety than C/C++.
3) Improved security. No buffer overruns or out of range subscript class of vulns.
4) Can more easily statically analyze to determine resource usage and inappropriate usage.
5) Can change the underlying HW platform and apps continue to run.
The only real issue I've seen with managed code in the past is perf. And from the game demos I've seen, I think they may have fixed that issue.
WP7 seems really nice. However, since you have no native C++ support games can't be ported from iPhone/Android. Basically you have to start from scratch in XNA. Somehow I don't all that many games will be released on this platform.
I think you may be right. Although, I don't think that's a great loss. Outside of literally a few games on iPhone, I think WP7 would do just as well with their own batch of games. I think XNA is a very effecient platform so I don't think developers need to port games. I wouldn't be surprised if there were 1,000+ games in mid-November.
I'm with the crew that thinks it's pretty short sighted to just dismiss this out of hand. Last time I checked, Xbox launched into a market place where people change their consoles a lot less frequently, with a single ENORMOUS player, and they've done pretty well for themselves.
The question is whether or not they get the amazing partnerships with HW/SW that Apple has driven into the iPhone and let them crush design. Without that, it'll be good, but not great and will not win the hipsters/design freaks.
The initial reviews have been great (even from Apple fanatics like Gruber, Mossberg, and Pogue). The WP7 development environment is great and utilizes APIs with a wealth of existing experience out there.
Sure they were late to the game, but from what I can see, they'll already become a player. The same dismissals were issued against Microsoft for other late-comers-that-became-hits like the XBOX series, Active Directory, and .NET.
I hate to say this, especially as an avid .NET fanboy, but I feel they missed a huge opportunity here. If they would have layered a pure-managed userspace on top of the CE kernel, they could've achieved extremely high performance (shared GC and seriously diminished task switching/IPC overhead) while guaranteeing a huge degree of security at compile-time. In addition, they could've much more easily moved the whole system to be orthogonally persistent, which I believe will play a big roll in the mobile space as tablets get more advanced, particularly.
The benefits of the OS being able to introspect completely on the applications running on it simply can't be overstated. From a security, stability, speed, memory use, and flexibility point of view, they missed the mark. It'd also open up a lot of new avenues in terms of parallelism, which will be a big deal in a few years as we get dual- and quad-core mobile chips. They're coming, and yet again we're not ready for them.
I sincerely hope they go the pure-managed-userspace angle for WP8. If they do, they'll have a tech stack that simply can't be beaten.
(Note: I'm a bit biased here, being the author of a pure-managed OS. But seriously -- these guys really started the trend, why are they not taking full advantage of it? They're already going mostly-managed...)
The worst news about this phone is the web browser: IE7 based with IE8 technology. IE7's still-buggy, slow rendering; glacial Javascript performance; no support for forward-thinking web technologies ("HTML5", canvas or webGL, CSS3). I hope this doesn't take off, or this will ruin the currently fun, Webkit-based mobile web development for modern smartphones..
Also, from a user's perspective: no Flash (at least initially) OR HTML5 video tag support? It's like Microsoft's totally missed the last few years of mobile phone flamewars.
In head to head comparison, the WP7 browser, in preproduction HW, performed about on par with Android (Nexus One) and iPhone 4 browsers.
I'm sure that with IE9, they'll rev the phone with an HTML5 focused browser in the future. But for todays web, I think a solid IE7/8 browser is something I'm completely fine with. At least for a year or so.
Don't believe so. Nor can you mount the media drive (as with Android). As a Linux user, this'll keep me far away from Win7 phones (as it did with iphones)
One aspect of the Windows phone that may be a big hit in corporations and governments is whole device encryption. PGP (now owned by Symantec) can deploy strong encryption to these Windows phones. Apple has always been difficult to develop for in this area (lots of frequent changes ISP can't keep up) and they tend to advertise to home users and I'm not sure about Android's whole device encryption ability.
69 comments
[ 3.3 ms ] story [ 89.9 ms ] threadI must admit though, I'm mostly excited to write mobile apps in C# and use XNA.
Though in a way, it almost doesn't matter. Microsoft has to offer the features of iPhone and Android to even be taken seriously, so we have to assume that is just there. What they really need can't be seen through promising text and screenshots, anyway: they really need polish.
Microsoft has been notoriously bad about leaving all kinds of holes in their products, so that they look OK on stage but end up feeling clunky as hell. If they are to have a chance this time, it is important that their phones feel simple and logical; and, dare I say it, they should even be a joy to use. Microsoft will never earn my respect until they can prove that they get this, and deliver it.
Neither Google nor Apple have offered many of these people what they want in a dev environment. Apple's required an odd language up until very recently, and even the C# language you can write to doesn't do many of the things they're used to doing C# in.
Android's development resources are capable, but Eclipse is a far cry from Visual Studio...
I assume tons of people will flock to the Win7 Phones unless they are just horrible once they get going.
Many game companies can target this platform much more easily than the iPhone/Android handsets as it also works off XNA.
Seems like its lack of OpenGL offsets that a good bit... yes, a lot of Xbox/Windows games will be easy to port, but it seems like more ports will likely to be coming from iPhone/Android.
My point is the tools don't matter as much as the strategy and decisions of Microsoft in other parts of the ecosystem to attract talent to produce content for their devices.
The world isn't all about consumers and flash. Whether or not they can win that market is an open question, but they'll make a dent. And Blackberry has built a very successful business doing just that (doing ok with consumers and crushing enterprise)
It's disheartening that so many bloggers are dismissing this awesome platform simply because Microsoft is "late to the game", yet they forget how successful Android has been. At this point, it looks like Google and Microsoft are fresh and new, whereas Apple is trying to prolong the life of an old platform.
The iOS folks got to start from near scratch, building on the foundation they already knew so well.
And I'd say they did a pretty great job.
Not only that, but I recall dismissing Xbox because Microsoft was so late to the game for video-game consoles that I thought they couldn't possibly have any impact.
Boy, how wrong I was...
Basically if I'm going to develop my hip new mobile app that's ready to take over the world I'm going to start with Android and iPhone and wait and see what OS I'm going to tackle next, and the way I'm going to figure that out is by sales numbers and right now even there are more Palm devices then WP7.
Microsoft already have huge developer mindshare. All they have to do is get developers that already use their platforms to use yet another of their platforms.
Android, iOS, Blackberry, etc.
I think that you're right that both are "successful." But I believe I'm not alone in thinking that the 360 was a far greater success.
edit: Further research shows 56% of browsers for September sport Silver light (http://www.statowl.com/custom_ria_market_penetration.php), but this is hard to compare apples to apples. Personally, to me a ~$300 purchase is worth a lot more then a free plug-in download anyway in terms of how successful something is.
I'm not sure I would classify Silverlight as "successful", just yet. Certainly it's getting buy-in in corporate environments, intranet apps, etc., it's visibility to the public still seems pretty small. Certainly there have been claims made (which I have no reason to doubt) that Silverlight has an install base of > 50% of the PCs on the internet, but I just don't see it having nearly the same "mindshare" as Flash or even HTML5. Now, this may all be a symptom of spending my browsing time on sites like HN and Reddit which are, if not anti-Microsoft, certainly not pro-Microsoft, so take this all with a grain of salt.
Amongst .NET developers Silverlight definitely seems to be popular -- I just don't know what portion of the overall developer population consists of .NET devs. As someone who spends a certain number of hours each day actually working on Silverlight-based stuff, I can say I like Silverlight, and it's the right tool for the job we're using it for.
After some reflection, I'm not sure what I would constitute as "success" in this space, to begin with. Is it driving a big video site like YouTube? I big gaming portal like Kongregate? I'm not sure those are great criteria for evaluating success, so perhaps my initial evaluation is off.
When I say Silverlight is "successful" I mean that it has gained a reasonable installation base (> 50%) in a short period of time (3 years).
In early 2009, Silverlight's installation base was only 20%, so it's clearly making inroads.
Will Silverlight ever get Flash-like install numbers? I doubt it, but I also don't think it needs to have those numbers in order to be considered successful.
If Microsoft could get the kind of adoption rates for WP7 as it has for Silverlight, I think they would be very pleased. Of course, phones are a little more difficult because it's much more likely to be a binary decision - people can have Flash AND Silverlight at no cost; I doubt there will be many people interested in owning an iPhone / Android phone PLUS a Windows phone.
It's become way too common to see people slagging on Microsoft gear without providing any kind of detail, so I'm just going to start asking them for some kind of backing data.
Now, if the OP had said "is this the next Xbox, or is it the next Kin?", then I probably wouldn't have had anything to say about the matter.
It seems more cut and dried in the phone space. Sell units, make happy customers, sell more units. Android is not necessarily making numbers 2 and 3. We'll see when iPhone hits Verizon.
Regular people already know about Android / iPhone. There are already cheap Android phones on sale (you can buy an unlocked Android phone, with no contract, for $300 ... see HTC Wildfire).
And many people are buying these phones for the apps available. For consumers the iPhone is king. Android is playing catch-up (but it is doing OK).
And speaking about regular people, my wife owns a WinMo 6.5 phone that will not see an official upgrade to 7 because it doesn't have the right hardware. And all apps for WinMo 6.x will have to suffer complete rewrites. So all the developers working on WinMo 6.x apps have just been fucked.
> At this point, it looks like Google and Microsoft are fresh and new, whereas Apple is trying to prolong the life of an old platform.
That's new to me, considering the iPhone 4 is still the best smartphone out there.
- The emulator is snappy and you don't need to mess around with ActiveSync.
- I'm not a huge fan of the XAML (the Silverlight/WPF markup language), but that is not an issue. I put a XAML place holder element in place and add controls in C#
- The built in controls look great and are surprisingly functional. I specifically thinking of the Panorama control - which allows application content to basically flow off screen. Some may find that style of having content get cut off by the edge of the display off-putting, but its effective if that truncated content is limited to titles.
- putting XNA in there is great, mostly for familiarity's sake. You still have to design for the phone differences (form factor, input, and library). Porting games over from XBox live probably won't require an enormous app-rewrite. Can't wait to see how this particular piece plays out.
The one drawback I can see has to do with Windows Phone store. I'm not really sure what the story is there. Is app distribution really limited to the store? How about enterprise apps?
I don't have experience developing iPhone or Android apps, so I won't comment on whether or not WP7 is better in that department.
I hope it's better than Apple's solution.
What we keep begging them for is the ability to point out users at our own enterprise app store, hosted on either Apple's servers or our own. It's also what I keep telling MS whenever I get a chance.
(PS: Send me an email? Would love to hear what you're working on)
MS won't kill this. I wouldn't let that be a factor on doing development. Now it may take a while for it to get consumer uptake. That may temper if you want to develop for it. But given that this device should sell moderately well with a good app store, it may have better ROI than the same app showing up in the Android app store, even with the larger number of Android devices.
There's a major new version of the dev environment underway, Xcode 4, which developers can already try for themselves: http://developer.apple.com/technologies/tools/whats-new.html
I've also played around with the Google Nexus One and the HTC Incredible. While they're great phones in their own right, the touch screen experience leaves a lot to be desired (atleast on those units) in terms of response time and accuracy + the camera on nexus one is nowhere near the iphone 3GS, forget iPhone 4.
Disclaimer: I have been using the iPhone since the past 3 years and currently on the iPhone 4. I think it's time that I tried a new platform because I'm simply bored of how the phone looks and how it operates (launch an app, exit an app, etc. for everything). I like the way multitasking is implemented and how well the camera performs. I've always had the craving for a hardware keyboard and it seems like the new Dell phone with WP7 is a good replacement for my phone, probably early next year.
I don't know whenever they will succeed or not, but it seems to be a hard task to enter the market when all rivals already have quite strong positions (including lots of software).
See for example: OS9 vs. OSX
The problem with MS, constantly, is that they have prioritized backwards compatibility over just about everything else - often usability, stability, and functionality. This has kept their platforms technologically backwards and their usability an infamous joke.
It's about time that MS started fresh with a modern, relevant platform. I just hope they can do something similar with desktop Windows.
Disclosure: I'm the project lead for Renraku, so I have a bit of a vested interest in seeing that happen.
I wholeheartedly agree, and from everything that I've seen of WP7, I'm impressed. MS has rethought the entire UI, and frankly, rebuilding from scratch was the only thing they could do to become relevant again in the consumer mobile space. They've done away with the desktop metaphor, menu bars and contextual menus, and yet they managed not to make it a carbon copy of iOS or WebOS. I can't wait to test it.
However, just a side note about your comparison between OS9>OSX and WM6>WP7: whenever there was a radical change in architecture, Apple provided a transition period where the two coexisted. When Apple switched from 68k processors to PowerPC, developers could build FAT Binaries that would run on both platforms. When Apple switched from MacOS 9 to OS X, MacOS 9 apps could still run within the Classic environment. When Apple switched from PowerPC to Intel processors, PowerPC applications could still be run within a layer called Rosetta.
Removing native code from 3rd party apps gives them several things:
1) Reduces incidence of memory leaks.
2) Less buggy apps w/ better type safety than C/C++.
3) Improved security. No buffer overruns or out of range subscript class of vulns.
4) Can more easily statically analyze to determine resource usage and inappropriate usage.
5) Can change the underlying HW platform and apps continue to run.
The only real issue I've seen with managed code in the past is perf. And from the game demos I've seen, I think they may have fixed that issue.
The question is whether or not they get the amazing partnerships with HW/SW that Apple has driven into the iPhone and let them crush design. Without that, it'll be good, but not great and will not win the hipsters/design freaks.
Sure they were late to the game, but from what I can see, they'll already become a player. The same dismissals were issued against Microsoft for other late-comers-that-became-hits like the XBOX series, Active Directory, and .NET.
The benefits of the OS being able to introspect completely on the applications running on it simply can't be overstated. From a security, stability, speed, memory use, and flexibility point of view, they missed the mark. It'd also open up a lot of new avenues in terms of parallelism, which will be a big deal in a few years as we get dual- and quad-core mobile chips. They're coming, and yet again we're not ready for them.
I sincerely hope they go the pure-managed-userspace angle for WP8. If they do, they'll have a tech stack that simply can't be beaten.
(Note: I'm a bit biased here, being the author of a pure-managed OS. But seriously -- these guys really started the trend, why are they not taking full advantage of it? They're already going mostly-managed...)
Also, from a user's perspective: no Flash (at least initially) OR HTML5 video tag support? It's like Microsoft's totally missed the last few years of mobile phone flamewars.
I'm sure that with IE9, they'll rev the phone with an HTML5 focused browser in the future. But for todays web, I think a solid IE7/8 browser is something I'm completely fine with. At least for a year or so.