I was just thinking about Mel Sampat’s clever OutSync that I blogged about yesterday. Microsoft obviously has some bright and talented software developers in its ranks. And, you know what? I think none of them should be involved in cutting a single line of code for clever stuff like OutSync? Why? Microsoft should be focusing its energies on just two problems: First, fix the horror that should not be named but instead has two names: ActiveSync and Windows Mobile Device Center (WMDC). This has been broken since Windows CE Services 2.0 (1.0 was actually pretty stable) for a decade now and needs to be fixed. Second, Internet Explorer. IE for Windows Mobile is damaged goods. Operamini gives a much better visual experience but suffers from its Java roots that creates a keyboard navigation problem for those of us who expect certains keys (like Back) to behave a certain way. Who know what happened to the Microsoft Labs SeaDragon project? It made a splash and then disappeared.
In the meantime, the Apple iPod touch is on its way to customers in the next three or four weeks. And, since a lot of Windows Mobile users already carry an iPod for their music and video, it isn’t much of leap to think some percentage (like me) will swap out their old iPod for an iPod touch and start playing with Safari on it. From what I’ve seen on the iPhone, it looks like a pretty good mobile browsing experience.
Comments
One response to “Priorities 1 and 2 for Windows Mobile 7 Should be Fixing IE and ActiveSync-WMDC”
Microsoft just released a closed beta for “deepfish” . Works alot like safari and Operamini 4 beta. check out the demo at the live labs website labs.live.com/deepfish. It looks sweet, I have been impressed with it’s performance anyway.