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 563625
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Microsoft won't listen
by jared_wilkes on Tue 4th Jun 2013 16:31 UTC in reply to "RE: Microsoft won't listen"
jared_wilkes
Member since:
2011-04-25

Metro may aim to be input agnostic, but it does so poorly.

Reply Parent Score: 5

RE[3]: Microsoft won't listen
by Nelson on Tue 4th Jun 2013 17:29 in reply to "RE[2]: Microsoft won't listen"
Nelson Member since:
2005-11-29

Tell me about it. They fucked up virtualization performance on non-Touch UIs which make any non-Touch scroll using a trackpad perform badly during UI container recycling.

Basically the XAML platform performs really well under touch, but something is out of whack with Mouse+Keyboard. It leads to a less than flattering impression on Mouse+Kb unless you design around the defect. It has to do with the scrollbar thumb jumping around during scrolling.

Now, on a broader sense I think they do the integrated Pointer events admirably and its certainly a HUGE step up from the situation in WPF/Silverlight.

If you're specifically referring to things that make sense from Touch (like Edge gestures) that don't make sense from a Mouse+KB then I agree. I also think that Right Click to bring up the app bar is problematic in that if you right click something which already shows a context menu, then the app bar wont show.

These issues, while real issues that affect real people, are not impossible for Microsoft to fix in a variety of ways. It makes more sense for Microsoft to fix them than it does for them to scrap everything they have.

Reply Parent Score: 3

jared_wilkes Member since:
2011-04-25

In both regards, but the former is (merely) technical. I think the poorly conceived UI/UX is the bigger, harder-to-solve problem.

And in more basic ways than just trying to be agnostic about input method. 1. Edge gestures (swiping in or out from an edge) are powerful. But they should be for functions also accessible by visual or other input methods and/or be highly discoverable and/or the vendor has to actively train or even re-educate users. 8 has done a poor job in all regards. 2. Hot corners are even less accessible to most users (there is little gestural reference to aiming for an infinite point, just a geeky-abstract mathematical understanding). Here, there is a problem with being agnostic, but they aren't being agnostic: a mouse is not designed to swipe from an edge, so hot corners becomes a substitute (maybe a substitute can be considered agnostic, but there are cases with no substitute: how do you close an app with a mouse?). Hot corners that activate edge-located UI elements trigger another button event and are confusing (aim for lower-right corner to activate, then move up two inches or some other length to hit Settings). 3. By dedicating right edge swipe to the equivalent of Control Panel and Search (which would be better grouped with an app launcher/Start menu), left needs to serve two rolls: app switching and multitasking (a very non-discoverable and difficult-to-teach gesture (swipe-in and out again)... so we'll also throw in the hot corner fallback too, with an even more difficult (not highly discoverable, not easily trainable, awkward to execute) slide-along-the-edge/press-and-hold downward gesture to switch to multitasking... 4. Etc...

They could still change a lot, they could provide more options (to enable/disable certain features or to change gestures), and they could get much better at educating their users still. But they don't have long to do this and I'm not seeing enough change to think that they will in time.

Reply Parent Score: 2