crashtestdummy
Platinum Member
- Feb 18, 2010
- 2,893
- 0
- 0
I think the best way to describe Windows 8.1 is confused. Microsoft wanted to have a unified interface for both tablets and desktops, but what they really did was create two UI languages awkwardly patched together by the start screen. The desktop environment (except for the start menu) is still largely the same as it ever was. There are actually some relatively nice tweaks that make it better (cf Windows Explorer).
Metro actually works quite well as a tablet interface in isolation. It's smooth, responsive, and it scales resolution much better than most systems. The swipe gestures from the sides, once you know they're there, are quite intuitive and have a satisfying tactile flair that Android (IMO) lacks.
The problems arise in the merger of these two systems at the Start/Apps Screen. The Start Screen first off defaults to the Metro interface, which leaves the desktop users frustrated (cf the thousands of threads and news stories around the web complaining). It would have been so easy to add the old start menu in as a "classic mode", which would have allowed users to wean themselves off of it over the next few years until the next version came out. It would have saved an enormous amount of pain, but it would have conflicted with Microsoft's long-term strategy (more on that in a bit).
The start screen, though, isn't a perfect solution for the Metro interface either. On Windows Phone 8 (a more pure implementation of Metro), you have the Start Screen and an "all apps" page, with a straight list of all installed software, easily browsable by first letter. On Windows 8, however, the all apps page inherits the file structure of the start menu, and desktop apps retain the extra icons and such that you're used to with Windows 7. This was ok when you had a directory tree with folders, but when you have a single screen displaying everything at once, it gets quite messy. Furthermore, while you can easily split the screen between multiple Metro programs, you inexplicably can't have one of those be the Start Screen itself.
All of this is further complicated by the fact that the desktop side of the (x86) operating system is as open* as ever, while the Metro side is closed (you can only buy Metro apps from Microsoft). Microsoft's strategy is that they want to compete with iOS as a closed tablet system where they get a 30% cut on everything sold. Ignoring for the moment that this goes against what made them a successful company to begin with (they were more open and widely available than MacOS or OS/2), it's an impossible business model while having an open platform on the same device. The only difference between making a touch-enabled, full screen desktop program and a Metro app is the ability to split your screen and API availability. If I were a developer, I'd see little incentive to make something specifically for Metro. My guess is that they plan to drop the desktop environment altogether in some future version of Windows, but I'm not sure they quite yet realize how disastrous that will be for them if they do so.
If I were them, here is what I would do: Merge Windows RT and Windows Phone 8, with the UI structure looking a lot more like WP8. I think it works better than the hybrid desktop/touch mess they currently have going on the tablets. Make a similar OS available for x86 Bay Trail chips, call it "Windows for Tablets", and sell it at the same price you sell RT and WP8. The version you sell for desktops and laptops (and you could pay extra for to put on a Bay Trail device) will still have both environments, but they'll be completely separate: desktop mode will have a start menu, and Metro mode will have a start screen. You could even give the option of an autodetect for convertibles.
*Note here that I define "open" as possible to distribute software independently of Microsoft, not Open Source. I apologize for the confusion, but it was the simplest terminology I could come up with.
TL,DR:
Metro actually works quite well as a tablet interface in isolation. It's smooth, responsive, and it scales resolution much better than most systems. The swipe gestures from the sides, once you know they're there, are quite intuitive and have a satisfying tactile flair that Android (IMO) lacks.
The problems arise in the merger of these two systems at the Start/Apps Screen. The Start Screen first off defaults to the Metro interface, which leaves the desktop users frustrated (cf the thousands of threads and news stories around the web complaining). It would have been so easy to add the old start menu in as a "classic mode", which would have allowed users to wean themselves off of it over the next few years until the next version came out. It would have saved an enormous amount of pain, but it would have conflicted with Microsoft's long-term strategy (more on that in a bit).
The start screen, though, isn't a perfect solution for the Metro interface either. On Windows Phone 8 (a more pure implementation of Metro), you have the Start Screen and an "all apps" page, with a straight list of all installed software, easily browsable by first letter. On Windows 8, however, the all apps page inherits the file structure of the start menu, and desktop apps retain the extra icons and such that you're used to with Windows 7. This was ok when you had a directory tree with folders, but when you have a single screen displaying everything at once, it gets quite messy. Furthermore, while you can easily split the screen between multiple Metro programs, you inexplicably can't have one of those be the Start Screen itself.
All of this is further complicated by the fact that the desktop side of the (x86) operating system is as open* as ever, while the Metro side is closed (you can only buy Metro apps from Microsoft). Microsoft's strategy is that they want to compete with iOS as a closed tablet system where they get a 30% cut on everything sold. Ignoring for the moment that this goes against what made them a successful company to begin with (they were more open and widely available than MacOS or OS/2), it's an impossible business model while having an open platform on the same device. The only difference between making a touch-enabled, full screen desktop program and a Metro app is the ability to split your screen and API availability. If I were a developer, I'd see little incentive to make something specifically for Metro. My guess is that they plan to drop the desktop environment altogether in some future version of Windows, but I'm not sure they quite yet realize how disastrous that will be for them if they do so.
If I were them, here is what I would do: Merge Windows RT and Windows Phone 8, with the UI structure looking a lot more like WP8. I think it works better than the hybrid desktop/touch mess they currently have going on the tablets. Make a similar OS available for x86 Bay Trail chips, call it "Windows for Tablets", and sell it at the same price you sell RT and WP8. The version you sell for desktops and laptops (and you could pay extra for to put on a Bay Trail device) will still have both environments, but they'll be completely separate: desktop mode will have a start menu, and Metro mode will have a start screen. You could even give the option of an autodetect for convertibles.
*Note here that I define "open" as possible to distribute software independently of Microsoft, not Open Source. I apologize for the confusion, but it was the simplest terminology I could come up with.
TL,DR:
- Microsoft has made separate touch and desktop interfaces, doesn't know how to merge them.
- I suggest separating them more completely.
Last edited: