Quote:
Originally Posted by Damien
The reason for enforcing the interface is the same reason they will require hardware to meet a minimum spec. Consistency across the devices which will help from a usablity standpoint but more importantly be much, much kinder to developers.
Developers can now develop applications knowing that the target hardware will behave in the same way across all devices. It will have the same features (i.e gps, higher definition screen, and so on) and it will look the same so they can match the style of their app to the style of the OS. Methods of interaction implemented by the OS can be implemented in these apps without fear that any of the style or function has been overridden on device x.
As mentioned before it gives Microsoft more freedom to refine and develop the OS without waiting for HTC or whoever to bring out an updated skin before it can be considered implemented on all devices.
|
Except it doesn't work like that Damien.
MS release updates to the manufacturers as they're the customers, and by applying the newer versions to new handsets it stimulates sales.
MS don't release updates such as from 6.1 to 6.5 for users to download, not because of hardware or interface differences, but because there is no financial case for it.
They already give manufacturers minimum spec for WM, I've not got a problem with that, it makes sense.
Customised interfaces sit on top of the OS not instead of.
I can shut down TF3D and have the WM6.1 interface.
So to insist that users have 1 interface doesn't make sense.
It's like with Windows 7 and getting rid of the classic start menu.
Not one of the W7 users at work like it.
Thankfully I've re-activated the quicklaunch toolbar on my W7 work laptop so I rarely have to click on the start button.
It reduces the customer base. People with look elsewhere or don't upgrade until they absolutely have to or something better comes along.