Windows Phones 7 Risks
2 min. read
Published on
Read our disclosure page to find out how can you help MSPoweruser sustain the editorial team Read more
It seems we are not the only one having a little hard time with the changes MS is doing with WP7, RedmondMag made a list of their possible risk. The list was created by one of their editors who managed to think up enough risk that MS is taking to make a full list. The list was so only that I just think its best if you read it yourself, in tacked.
- Tailoring the platform for consumers rather than for business users. (Yes, I know the ‘Softies are saying Windows Phone 7 devices are being designed for both consumer and business use. But the reality is that Windows Mobile is Microsoft’s enterprise mobile play and Windows Phone 7 is its consumer play.)
- Going with an entirely new — and far more locked-down — UI known as Metro, which Microsoft pioneered with Media Center and the Zune HD.
- Deciding against providing cut-and-paste functionality in the first release of the Windows Phone 7 platform.
- Opting against enabling multitasking for third-party applications.
- Selecting Silverlight and XNA as the development environments for Windows Phone 7, meaning programmers will have to create applications using managed code and using only the C# programming language.
- Providing no backward compatibility, meaning Windows Mobile 6.x apps (even Microsoft apps, like Microsoft Office Mobile 2010) need to be rewritten to run on the new mobile platform.
- Requiring all application downloads and purchases to go through the Windows Phone Marketplace.
You can read the full write up here and comment on what you read.
Update: I think you guys think we all here at WMPoweruser are being too negative towards the new OS. I for one is surely not. I really do not care that it might not have all these things. I am still going to buy it, and live with it, and love it. I am not a business user, so its nothing too important to me that some of these features are missing.
User forum
0 messages