The Windows 8 Power Struggle: Metro Vs Desktop
MojoKid writes "Metro, Microsoft's new UI, is bold; a dramatic departure from anything the company has previously done in the desktop/laptop space, and absolutely great. It's tangible proof that Redmond really can design and build its own unique products and experiences. However, the transition to Metro's Start menu is jarring for some desktop users, and worse yet, Desktop mode and Metro don't mesh well at all. The best strategy Microsoft could take would be to introduce users to Metro via its included apps and through tablets, while prominently offering the option to maintain the Desktop environment. Power users who choose to use the classic UI for desktops and laptops can still be exposed to Metro via tablets and applications without being forced to wade through it on their way to do something important."
http://www.winsupersite.com/article/windows8/windows-8-consumer-preview-call-common-sense-142476
Also, try to spend a few minutes learning shortcuts etc. before dissing the experience. It's not a SP for Windows 7, it's a new OS.
http://arstechnica.com/microsoft/news/2012/02/getting-starte...
http://www.kotaku.com.au/2012/03/windows-8-tricks-tips-and-s...
And it will enable many devices like these that don't exist now:
Idea Pad Yoga: http://www.youtube.com/watch?v=Yz2R9y9ZvkA&hd=1
Samsung x86 Tablet: http://www.youtube.com/watch?v=w8-K1ELv6DE&hd=1
Try doing that with an iPad.(There are iPad-like ARM Windows 8 tablets too that won't run x86 apps but which will have Office).
83inch displays: http://www.theverge.com/2012/2/29/2833173/windows-8-82-inch-...
All these form factors tied in the with the vast Win32 ecosystem(except ARM tablets) and a single Touch-first Metro ecosystem.
It's interesting how the comments on Apple/iPad/Post-PC articles, financials of Apple/Dell/HP etc. state that "MS is dying in the Post-PC" era, but now when they come out with a solution to make a OS run on different form factors and to have tablets that are not just consumption devices, the comments on here are skewed towards "Why change something that works?". If PCs are really dying, why not attempt to fix that instead of standing by with their head in the sand(like RIMM)?
There will always be people unhappy with anything you build or change. They should just go with their vision of what they think is right and that's what they did. They envision that with Windows 8, most new monitors will be touch enabled because of the demand so that for some functions(like clicking on links), people can use touch.
You may disagree with the vision, but you can't disagree that there is a method behind the madness.
This space for rent.
I think Microsoft Operating Systems follow the trek movie rule: Every other release sucks.
#fuckbeta #iamslashdot #dicemustdie
MS had, basically, two options: create a new brand for an OS tailored for post-PC devices, or continue with what they had. They chose to create a new (and pretty good, actually) interface in Metro, but then apply it to both post-PC devices and PCs and brand it as Windows in both places. I think that I would have gone the other way, creating a Metro brand to go with the interface, and tailoring it even more closely to post-PC systems, while keeping the Win7 interface on the desktop, and sharing the underlying kernel and as many APIs as possible between the two variants. Time will tell if that was a good decision or not; it was certainly a bold decision, given the success that Apple and Google have had with specific post-PC brands and interfaces.
-- Two men say they're Jesus. One of them must be wrong. - Dire Straits
Failed web "designers" are ruining GUI applications left and right. It doesn't matter if they're open-source apps or if they're closed-source commercial apps. These self-labeled "UI designers" and "usability experts" get involved with a popular project that had a usable UI, and they completely trash it.
This has happened to GNOME. This has happened to Firefox. This is now apparently even happening to Windows!
Somehow, these "designers" have managed to create UIs that are far worse than even non-artistic programmers came up with. Firefox is a perfect example of this. The earlier releases had very usable UIs. Then came Firefox 4, and the entire UI was shit upon. Each subsequent release has fucked up the UI more and more. Now we don't have menus by default, we don't have a status bar by default, and Firefox is damn near unusable without heavy tweaking to re-enable such basic UI elements!
The only appropriate thing to do is to shun these people. It doesn't matter which project it is, or what sort of application is being developed. Refuse their contributions. Refuse their ideas. Shoot down their suggestions in mailing list discussions. Don't allow them direct commit access to any source code. Ensure that bugs are logged regarding their horrible designs, especially when usability is impacted.
We need to go back to software developers creating UIs. Maybe they're not artists, and maybe the UIs they built weren't "pretty" (a.k.a full of curved corners and gradients), but at least they were intuitive and we could use them to get real work done efficiently. We can't do that any longer, now that "designers" are trashing every UI they come into contact with.
Let's see; I work on two 22 inch monitors. I can move from the far left edge to the far right edge with a three inch movement of my mouse. Now you want me to have to lean toward the monitors and move my arm over three feet to accomplish the same thing. How ergonomic! How NEW! How efficient!
Someone will find a way to get it back to me. YOU'LL NEVER TAKE IT FROM ME!
I write professional videogame reviews! http://www.digitallydownloaded.net/
I travel a lot, all over Europe, North America and Asia, and I've come to realize that tablets are basically a myth. While there is a lot of hype around them, and many have been sold, almost nobody actually uses them!
During my travels, I see people using cell phones. I see people using smart phones. I see people using laptops. I see people using netbooks. I see people using desktops. But it's extremely rare to see anyone using tablets. I see literally thousands of other people using smart phones for every tablet user I see.
I visit all sorts of environments, from huge corporate offices, to parks, to restaurants, to planes, to universities and colleges, to airports, to train stations, to city squares, to government offices, to subways, to cafes, to so many other places. Given the amount of traveling I do and the huge number of people I see in any given day, and given how much we hear about tablets, I should be constantly seeing people use tablets. But I just don't.
I think that they're the kind of device that somebody buys because of the marketing hype or because they sound like they might be useful, but then in practice they turn out to be feeble and impractical. Then they sit there on a bookshelf or table top, completely unused, until they're all but forgotten about.
I'm sure a bunch of people are going to reply to this saying how they find tablets useful in some very niche situation, but these are indeed very niche cases. The widespread usage of tablets just isn't there, like it is with smart phones or even netbooks. The popularity of tablets is a marketing myth, I suspect, rather than a reality.
If there are no on screen visuals I'm lost. I rarely use keyboard shortcuts and I can see that increasing when there isn't a keyboard.
The problem I have with Metro is that it's so hard to organize things. I have over 1000 shortcuts currently on my Windows 7 machine, where are they supposed to fit in Metro. I'd need to scroll for a week to find what I'm looking for. "Oh, but you can just type the name of what you are looking for. " but I don't remember the name just what the icon looks like. Keep your Metro, give me a start menu and we can both be happy.
... Apart from Metro only being useful if you have a laptop/tablet/smartphone (touch screen Desktop/TV never worked!)
Was that both GUI's weren't linked, they were in essence 2 separate desktops.
So if i opened IE (or any other program) on Metro and had to switch to the "other" desktop, If I opened IE there it was a totally new session. (I'd think it would be better, or nice, to ask the user if he wanted to pull the session from metro.)
i gave it a week of use, then wiped it.
Laters Sol "Have you found the secrets of the universe? Asked Zebade "I'm sure I left them here somewhere"
I mean Star Trek 3 was good. I mean Reverend Jim the Klingon for FSM sakes.
Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
Problem is they fucked up the setup on the desktop. On an embedded device, Metro is everything. Makes sense, it is the embedded GUI, and they can't run PC apps. So you fire up the device, Metro is what you get.
However on a PC, the desktop should be what you get, Metro should be something you open in it. That way you can run Metro apps if you want, which is cool, but on the terms of a desktop. You can let them run full screen, or not, put them in a window. It'll seem "full screen" to them, they'll just be told that window is their screen.
The reason is the multi-window paradigm is what works for desktop computing. It is an efficient way to work with multiple programs, which is what almost everyone does. Even non tech types. It is efficient to be able to open up multiple things, arrange them as you like, switch between them easily, and so on.
The smart phone idea is not an efficient way to work, it is just a necessary one given the limitations of the platform. Trying to force it on the desktop is rather stupid.
I can see the benefits of sharing a codebase, but the fundamental interface is going to need to remain different.
I hate to say this--but this concept of 'Apps' that everybody is latching on to--it is a huge pile of steaming buzzword. Yes their are applications, but the concept that all of computing can be neatly tucked and packed into an easily marketable single purpose flashy shiny big round button GUI software as a service plug in API model full of synergism and one-click-wonder wow--perhaps, but not for the power users, not for enterprise. There may be a day, but it isn't this decade IMO. I understand how consumers want this and blah blah rah grandma simplicity blah new age computing blah ease of use apple blah, but I'm here to comment about Apps and how I hear that word used in the wrong places (IMO).
Where's my 'app' for DBA activity? Where's my simple one click 'app' that monitors hundreds of servers, routers, switches? Where's my 'app' that automates my build processes? Where's my app that gives my complex analysis of all my interconnected nodes? You wont find them--not soon and not on 'markets'. Because these are complex intertwined multi-APPLICATION, to use the full word, work-flows that require desktops or complex usage of scripting and consoles. Sorry but for power use, it's just the way it is, in this decade and probably a few to come. These things can be done well and simply, but not without serious power-tools and planning.
Let's me honest, computing has been around for decades now, and even though on the consumer level 'apps' reign supreme it seems, there will always always always be power users who will need more complex environments for the vast array of software suites, tools, languages, and utilities needed to maintain and administer complex networks for build processes or whatever. Perhaps there will be a day when it is all unified. But that would require vast cooperation across industries, standards bodies, companies, open-sources houses, etc. Until some defacto design standard from layer 1 to 7 and from user space to kernals to whatever is implemented across the industry, nothing will ever be 'simple apps' while separate unique tools and such exist--thus guaranteeing the lifetime of the terminal and the desktop. It seems we are now defining apps as "guis that are flashy, sleek, use large rounded buttons, and have limited functionality', well, there's many of those out there. End rant. (the word app just sets me off)
'We are trying to prove ourselves wrong as quickly as possible, because only in that way can we find progress.' RPF
My gut feeling is that Win 8 is going to be a spectacular failure like Vista. People who buy PCs with Win 8 loaded are going to throw a fit and demand a downgrade to Win 7. Microsoft will survive because no matter how much they screw up, the competition can't really take their place. So it's not necessarily a bad gamble for Microsoft. It might work. I doubt it, but I could be wrong. If I'm right then after it fails and they get burned by the "not gonna buy it" and "I demand a downgrade from this crap" crowd, they'll quickly re-design WIn 9 to look like Win 7 with some added features and put that out.
Face it, nobody likes it.
Any time you find yourself explaining Why People Should Like Your Stuff if they Only Used It Right, it means you have failed Marketing 101 and need to turn in your diploma, because you obviously weren't paying attention in class.
(my first degree was in Marketing, fwiw)
-- Tigger warning: This post may contain tiggers! --
An article that everyone (including plenty Slashdotters) see when they open Microsoft Visual Studio today:
Create your first Metro style app using C++
[This documentation is preliminary and is subject to change.]
A WindowsMetro style app is tailored for the user experience that's introduced in Windows 8 Consumer Preview. Every great Metro style app follows certain design principles that make it look more beautiful, feel more responsive, and behave more intuitively than a traditional desktop app. Before you start creating a Metro style app, we recommend that you read about the design philosophy of the new model. You can find more info at Designing Metro style apps.
Here, we introduce essential code and concepts to help you use C++ to develop a Metro style app that has a UI that's defined in Extensible Application Markup Language (XAML).
If you'd rather use another programming language, see:
Create your first Metro style app using JavaScript
Create your first Metro style app using C# or Visual Basic
Objectives
Before we start coding, let's look at some of the features and design principles that you can use to build a Metro style app with C++. It will also be helpful to look at how Microsoft Visual Studio 11 Express Beta for Windows 8 supports the design and development work. And it's important to understand how and when to use the Visual C++ component extensions (C++/CX) to simplify the work of coding against the Windows Runtime. Our example app is a blog reader that downloads and displays data from an RSS 2.0 or Atom 1.0 feed.
This article is designed so that you can follow the steps to create the app yourself. By the time you complete this tutorial, you'll be prepared to build your own Metro style app by using XAML and C++.
Comparing C++ desktop apps to Metro style apps
If you're coming from a background in Windows desktop programming with C++, you'll probably find some aspects of Metro style app programming to be very familiar, and other aspects that require some learning.
What's the same?
You're still coding in C++, and you can access the STL, the CRT, and any other C++ libraries, except that you can't invoke certain functions directly, such as those related to file I/O.
If you're used to visual designers, you can still use them. If you're used to coding UI by hand, you can hand-code your XAML.
You're still creating apps that use Windows operating system types and your own custom types.
You're still using the Visual Studio debugger, profiler, and other development tools.
You're still creating apps that are compiled to native machine code by the Visual C++ compiler. Metro style apps in C++ don't execute in a managed runtime environment.
What's new?
The design principles for Metro style apps are very different from those for desktop apps. Window borders, labels, dialog boxes, and so on, are de-emphasized. Content is foremost. Great Metro style apps incorporate these principles from the very beginning of the planning stage. For more info, see Planning Your App.
You're using XAML to define the entire UI. The separation between UI and core program logic is much clearer in a Metro style app than in an MFC or Win32 app. Other people can work on the appearance of the UI in the XAML file while you're working on the behavior in the code file.
You're primarily programming against a new, easy-to-navigate, object-oriented API, the Windows Runtime, although Win32 is still available for some functionality.
When you use Windows Runtime objects, you're (typically) using C++/CX, which provides special syntax to create and access Windows Runtime objects in a way that enables C++ exception handling, delegates, events, and automatic reference counting of dynamically created objects. When you use C++/CX, the details of the underlying COM and Windows architecture are almost completely hidden from your app code. But if you prefer, you can program directly against the COM interfaces by using the Windows Runtime C++ Temp
Parenthetically, why don't you ever see in Star Trek someone cleaning the fingerprints and accumulated grunge off all those touch screen displays? There must be a janitorial service just to do that.
Oh, because it's fiction, that's why.
Now that I think of it, that might make the basis of a story. A janitor forgets to lock out the navigation console, juices up his rag, and sends the ship Where No One Wants To Go.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Why are all my computer interfaces being transformed into children's toys?
Why are my menu bars, tables, and text boxes being replaced by coloured icons dancing around the screen. Am I expected to just intuitively "feel" where all the programs and options are now?
This isn't just an OS problem. It happening across the program spectrum and I blame the influence of smartphones and similar touch oriented devices.Speaking as someone who has never owed a smart phone I have always found them restrictive and confusing. Using one is like navigating a theme park without a map. Eventually you'll want to just find a place to sit down but you'll only get more lost among the theme rides and hot dog stands.
If this nonsense gets rolled out onto computers that people are supposed to be working on, it will either precipitate a recession or an injunction by employers groups. Either way, I'm sticking to menubars.
May the Maths Be with you!
All I want is an option in the Control Panel that says "Completely disable Metro UI. I understand this will prevent me from installing, launching or utilizing Metro Apps. This will enable the classic Start Menu and will make the Classic Desktop your only operating environment." Problem solved. Just fucking humor us.
OK, I resist change just like everyone else. But that's not what is going on here.
Monitors are getting bigger. I'm doing more things at once. I want better ways of managing that. But Metro just gives me one thing at a time. Sorry, that's not a solution to the problem. That's going back to the original Macintosh.
Apple isn't perfect, but at least they've been trying some new ideas. I don't think the new ideas on screen management have been all that successful, but at least they're attacking the right problem.
At the moment, nobody has a better idea for a smart phone or a tablet than to show one app at a time. The only way W8 makes sense is if they're adding a piece for portable devices, and said "while we're at it, let's let desktop guys use it too." Fine. But only if they realize that the desktop systems still need new ideas as well. And if I were doing a ground-up redesign, I'd consider whether we might be ready for a better approach with tablets as well. The new iPad has more pixels than many monitors. I'm not sure one app at a time should be the only way to use it.
The problem is
it is devoid of functionality and reeks of lets make everything stupid. ideology that has become the keystone of this decade.
yes these words are polarizing but the whole interface is polarizing. im not just talking windows here im talking all smart devices and its "thinking behind its poor design"
remove functionality .
remove options.
apply bare minimum usability.
when you come from robust desktop apps that give the users control of their programs , it is a slap in the face to use a so called smart app. and if you want to close the app ? forget it buddy the all knowing software engineer has removed the "confusing" close app functionality and gently suspends the application in the back ground . so if it glitches, it remains glitched until you reboot the device .
We have taken leaps backwards in the progress made in user interface in the last 20 years . instead of having things available to you with a few short clicks you are now bombarded with hundreds of lil shiny buttons across multiple virtual desktops that you have to examine to see what they are . (oh press the wrong one no problem well just suspend it into the background until you need it again !!)
Also the new interfaces are designed with the mindset that are to be only presented not used . so screw copy, screw paste, screw edit, and screw select all you dont need it !! just look at the pretty pictures and post your short expressions of glee on facebook.
so yeah dont expect those of us who actually use our computers be enamored with a another dumb user interface . just because it is touch touchy touchy does not mean it is gaining more functionality . in fact in most cases we are loosing a majority of progress that was made in application useability .
Music the Paint dancefloor the canvas your body the brush
Wow, that's one more adjective than I've ever seen that apostrophe substituting for. But get on with your bad self, anonymous grammar cop. And everyone remember, punctuation is critical. "Let's eat, Grandma" is not the same as "Let's eat Grandma."
-- Two men say they're Jesus. One of them must be wrong. - Dire Straits
If there are no on screen visuals I'm lost.
This is very true. It's a problem with a lot of touch-centric UIs: There are no onscreen hints or anything to explain to you how to use the UI.
Anyone who has ever used a word processor can sit down with Microsoft Word and write a letter. There will probably be things you don't know how to do, so you'll end up searching the Ribbon to find them. But that's just it -- you can find them. There will be icons there and the icons will have labels that say things like "Insert Date/Time."
Metro, on the other hand, has a few clever icons, but they don't necessarily mean anything to someone who has never seen them before. Some of the other functions involve gestures or moving the cursor to just the right part of the screen to activate a feature. I found I had to stumble around awhile before I knew how some of the most basic navigational controls worked.
Note: I didn't say search around, as you'd have to do with the Ribbon. I said stumble around, meaning I had to try mouse movements and push icons without knowing what they were actually going to do. Inevitably that meant I'd end up activating controls I hadn't meant to. I might luck out and find the thing I want, or I might immediately think "Undo, Undo, Undo" ... but of course, Undo might have been the thing I was looking for in the first place. This is a lousy way to learn a UI. It's a step back from what we've grown accustomed to.
Breakfast served all day!
..and absolutely great
At my job I'm already working with Win8 a little, and I don't think it's so damned great. It holds your hand like you're a silly child and hides even more from you than any version of Windows I've ever seen. I suppose if you're looking for the OS for the most dumbed-down generation ever then it's great, but for those of us who want something functional and powerful, I think it's a huge flop.
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
The designers have taken over. We will never the see the likes of Douglas Engelbart again.
I remember the push back I had back in the early 00's when I had the temerity to suggest that icons in a toolbar should have a descriptive text placed below them, on the basis that it makes the icons discoverable. Most of the objections were because "it looked ugly".
Just looking at the Chrome instance I'm typing this in I see users are supposed to know that a grey spanner means "Settings". Ho hum.
Syllable : It's an Operating System
Designers don't think computers. They think bunnies and lolcats and premium blended marijuana.
Programmers think computers. You want a button ? Okay, [button] here's a button. It's too square looking ? Okay, (button) here's a rounded button. Too plain ? Okay, {.,-'button'-,.} here's a fancy button. Too ugly ? Okay, *deletes button* talk to me when you actually want to click the damn button.
End users can't design for shit. They will have an opinion if you put something in front of them, but to ask them to come up with an interface from scratch will not yield any results. They don't know what they want to do until you tell them what they CAN do.
-Billco, Fnarg.com
I'm really trying to work with this. Other than Metro, Windows 8 isn't bad. It's actually a marked improvement over Windows 7. The biggest change is the number of windows I can manage and keep open with 4 gigs of RAM. Memory seems to be cycling by itself with no third party software, registry hacks, or manual optimization. Silverlight is better on my 2gb Gforce card. Netflix is clean, and looking great. On Windows 7, the picture was muddier. So in terms of the things I care about (lots of open windows and netflix) Windows 8 is a boom.
What I'm not impressed with is the way Metro is locked down. I downloaded Visual Studio 11 beta so I could start writing Metro apps, and was immediately reminded that Microsoft will be approving any and all Metro apps, but they're letting me run my own stuff out of the kindness of their ever loving little hearts. That annoyed me, and it made me question my motivation for wanting to write Metro apps in the first place.
I mean, I can write an Android app today, compile it into an APK, and it'll run on any Android device within the scheme I compile for. Google doesn't and shouldn't care about the apps I write, and I like it that way. I don't really see the point of building something in the first place when someone who has nothing to do with anything can control my ability to publish it. If there's any chance of rejection at all, why should I bother to begin with?
I'm not learning new platforms because I like new platforms (well, I am, kina), I'm doing it because I want to have viable programs that I can do things with.
Screwing with my ability to publish my work is not a way to launch a new product.
I'm sorry. It's totally unacceptable.
But are you retarded? You can't remember the name of something but you can recognize thousands of icons designed for 16x16 display?
You don't have to be retarded to be slowed down by a less-than-optimal interface. Every brain cycle you have to burn figuring out a sub-optimal GUI is one less brain cycle available for actually getting your work done.
Little things like this might seem trivial, and they are, but the cumulative effect can build up to the point where your productivity is significantly less than it could have been.
I don't care if it's 90,000 hectares. That lake was not my doing.
What I don't get is the obsession for "search" in new desktops. Must I now use search to find my apps too?
I never use the file search tools either, as my files are nicely enough organized in directories. Well, maybe the unix "find" command is nice sometimes.
It's not the UI.
It's the way MS treats its users. The main difference between MS (who couldn't get rid of the "Start" menu for close to 15 years even though their final user testing prior to launching windows 95 revealed that it was a horrible, broken idea) and Apple (who can seemingly come up with a new paradigm for the iPhone/iPad and have it accepted) is in how they think.
MS thinks like developers. So when they have an idea they like, they force it on the users. And if the users don't accept it, they force it some more.
Apple thinks like designers. If they have an idea, they test it out and refine it until the users love it.
And that's why this would have worked if the one Steve had come up with the idea, but it'll be an epic fail in the hands of the other Steve.
Assorted stuff I do sometimes: Lemuria.org
I'm a massive Stardock fanboy, been a supporter or theirs for a long time. I've no worries that if MS fucks up and drops the ball someone, Stardock certainly and probably others, will pick it up.
However I'd rather they didn't. I don't want to be having to tell users to get 3rd party software to make their OS not suck. I don't want to have to customize an enterprise environment to be non-standard.
The thing is if MS makes it suck realistically what'll happen is people will just stick with Windows 7. Windows 8's largest competitor will be 7. 7 is a really good OS. It is solid, easy to use, and so on. People aren't sitting here going "Man I need a new OS, this one is crap," they are happy with what they have.
So Windows 8 needs to be better to woo people over. Now I think some of the ideas they had were better. As I said, the ability to run Metro apps is a great one. See an app on a phone you'd like on the desktop? No problem, just grab that shit from the store and it works. Brilliant. However if they fuck the interface up badly so people have to fight to use it, they'll give it a miss and stick with 7.
That makes me angry because supporting old versions of software sucks. Now while Windows 7 is still new, it'll create a 7 rut. People will decide 7 is the One True OS(tm) and refuse to upgrade. So 10 years later I'll be forcing people off of it because it is going out of support and Windows 9 or 10 or whatever WILL be a good OS but they won't want to change because they are convinced 7 was the last good OS EVAR.