Why is an unverified rumour, about Windows Mobile/Phone 7, creating such a buzz today? Two different sites, although PPC related, posted details today of an “anonymous” email, detailing important changes to WinMo 7. A few points in the information are pointing to a major restructure of the OS, that makes it comparable to the Apple model.
No Multi-tasking:
No Multi-Task support. Applications will “Pause” when in the background, however will support notifications via push notifications.
No Cab Install
Windows Phone 7 will only support application installation through service based delivery. (i.e Marketplace). Application installation via storage card will not be possible
No backwards compatibility for .Net CF
-No NETCF backwards compatibility. This means the original rumor of no backward compatibility for applications holds to be true. That being said, there are high hopes of porting the NetCF to the newer platform easily
No Customisation
OEM Interfaces will not be allowed to run on the device. Say goodbye to Sense UI / SPB Mobile Shell / Point UI / Infinity, etc, etc. etc.
If this was all true, where would Windows Mobile stand?
Would Microsoft depart so thoroughly from their traditional framework for Windows Mobile in one foul swoop, or is this evidence of the difference between classic and professional versions of the software in the future?
The full text of the anonymous email
· WP7 will be announced at MWC, and there will be a demo, but this will be just the UX
· MIX will have specific developement focus sessions on WP7
· WP7 supports both Sliverlight (out of browser) and XNA
· Silverlight is version 3.0, with elements of 4.0 plus mobile specific features such as sensors etc
· XNA apps can be developed using XNA GameStudio 3.1
· SL apps developed using Expression Blend 3.x and VS2010
· MS will release a mobile version of VS / Expression which will be free, and VS2010 / Expression Pro will have a free add-on
· WP7 will have an equivalent of .NET CF embedded into SL, but no SQL.
· WP7 will have isolated storage which is accessible using LINQ
· The UX of WP7 is based upon a theme called “METRO” and is similar to Zune HD, but with a completely new “Start” screen.
· No multi-tasking (applications will pause when in the background, however they will support notifications using the MS Push Notifications environment)
· No .NET CF backwards compatibility, however a proportion of the data and business logic in .NET CF could be ported
· MS were confident to have devices ready for Sep 2010
· No MS manufactured device, however much tighter control of manufactring process, so as an example each device has a 3D processing chipset, and MS provide all of the device drivers. So no platform builder. This enables OTA updates and simplified model for ODM’s
· Marketplace will support buy and try before you buy, as well as an API
· ODM / OEM will not be able to modify the “Start” screen, so no more HTC Sense / TouchFlo etc.
· MS are actually ahead of schedule which will surprise the analysts / journalists
· Browsing experience is currently faster / better than iPhone 3G, and they are aiming towards 3GS.
· Browser is based upon desktop IE7 codebase, but with some IE8 functionality
· No in browser Flash or SL
· WP7 has full integration with XBOX Live, and ability to purchase games
· WP7 will use the Zune software for music, videos, photos sync
· WP7 only supports app installation through service based delivery i.e. marketplace, so no side-loading
· MS will provide a hosted push notifications environment
IMHO, a lot of this seems feasible, and a lot of it seems like speculation. The points I highlighted are the major strengths of Winmo, with those disabled, it would not be nearly as useful as a mobile computing platform. Possibly, Microsoft intend a strictly controlled entertainment driven smartphone targeted at limited usage consumers, but I can’t see them abandoning the enterprise market. We’ll find out in little over a week I suppose!
WinMo7 Rumour, Unpalatable!
You must log in to post a comment.