Linked by snydeq on Tue 4th Jun 2013 01:46 UTC
Windows First looks at Windows 'Blue' have revealed an upgrade composed of cosmetic fixes, suggesting that Microsoft may be blowing its chance to turn the tide on Windows 8 blow back, and make good on its promise to truly 'rethink' Windows 8 with the release of Windows Blue. As a result, InfoWorld has issued an open letter to Microsoft to consider Windows 'Red' -- what InfoWorld is calling a 'serious plan' to fix the flaws of Windows 8, one that could rescue Microsoft's currently flagging promise to deliver a modern computing experience on both PCs and tablets.
Thread beginning with comment 563548
To read all comments associated with this story, please click here.
dpJudas
Member since:
2009-12-10

This Windows Red proposal makes a lot of pointless technical choices that make little sense, such as requiring a reboot between mobile and desktop UI's in their Duo version.

The real problem with Modern is that an application UI is either designed for touch (fat fingers, etc), or it is designed for keyboard and mouse. Microsoft literally lost the entire mobile market because they kept on trying to push the desktop UI in the Windows CE age. Then Apple showed how you really needed to redesign *every* UI for the different interface. And sadly then with Modern Microsoft revealed they still doesn't get it by trying to shoehorn a mobile UI on the desktop instead.

My version of Windows Red would not require artificial reboots or try to allow mobile app UIs on the desktop. They will always feel crap there. Instead I would make every application support two different UIs, and depending on the input method for the screen I would present either one user interface or the other.

For example, if you sit down at your desktop machine you'd see the Windows 7 desktop, and if you RDP'ed to it from your tablet you'd be presented with Modern UI for the same open applications. Only if you explicitly requested it would you be able to see the wrong UI type for the input method. No reboots or special editions required.

Reply Score: 12

Nelson Member since:
2005-11-29

The problem is that mouse and touch can be used at the same time at random. I can be touching a Metro app on my Surface then switch and use the trackpad depending on what I feel like doing. That's not a strongly supported scenario under your plan.

I think the Metro stuff is overblown, sure there needs to be more developer guidance, but I'm 100% convinced that it is possible to write a single app that supports Mouse+KB and Touch adequately.

There is a learning gap and it will take time for more and more developers to get up to speed with writing excellent Metro apps, but they will get there eventually. At the same time, Windows Blue gains important WinRT APIs which should enable new classes of apps. Expect this to continue as Windows is further developed.

Eventually, WinRT will support a lot of the same scenarios that Win32 supports today.

Reply Parent Score: 3

Fergy Member since:
2006-04-10

I think the Metro stuff is overblown

We all think that. But not in they way you mean.
, sure there needs to be more developer guidance, but I'm 100% convinced that it is possible to write a single app that supports Mouse+KB and Touch adequately.

Sure with a lot of effort you could get it to adequate. It would still be a fullscreen app so useless to people who want to be productive.

Reply Parent Score: 2