|
Dropping a few million to buy away some UI designers from Apple would be a start.
Then I'd tell the development team that changes like removing BT DUN or sync over wifi will be forbidden.
Once they are done turning the X into a close button I'd let them continue to start from the ground up, adding the few parts of WM that don't suck, and telling the developers to rewrite the parts that do.
Parts we wouldn't see again:
Connection manager
Calculator
IE in its current form
PocketOutlook
Program manager
Microsoft Bluetooth
What we'd end up with is a more polished UI.
A browser that is a TRUE mobile browser (with integrated support for flash, media and java), tabs and a smarter rendering engine.
A much easier to use connection manager that supports configuration on the desktop (no more entering 40 character keys on the device).
A configurable program manager with different views (list, icons etc...)
An email client with filtering, spelling check, flagging and other features.
The Bluetooth stack will be purchased elsewhere since there doesn't seem to be a single programmer within Microsoft that can develop a reliable working stack.
Then, before releasing this, I'd tell the operators that they are no longer in charge of updates. Updates and fixes will be released when they are ready and can be downloaded OTA or through activesync. Operators can put their own .CAB package on the device as long as it doesn't interfere with the core of the OS.
Next up are the hardware vendors. They will cease to use QVGA from 2008 onwards and only release VGA and higher. The minimum memory will be raised to 512Mb.
|