I didn't realize this. In fact, if I were asked to guess, I would have answered that most new users would pick up pretty quickly how to use context menus, especially if the context menus had related commands like file manipulation if in Windows Explorer (is it still called that?), or formatting if in a text document, etc.
Hell, rats in a cage can learn what to push in order to eat, so I would have thought that people would be able to learn this. Of course, it would help if they were told somehow and didn't have to discover it.
I would argue that THIS is what made Apple's OS hang on all those years it was in the severe minority. There is a segment of the population that wants only one mouse button to click, not 3, not 3 plus CTRL or ALT or etc. Apple did end up having to rely heavily on their option key to extend functionality but at its root the UI was designed so that the average user could do things in a simple, straightforward way. MS sees visually exposing commands to the user as their way to do it and while I may not entirely agree, I don't think it's without merit. My kudos to them for also letting me as a "power user" collapse the "newbie visual noise" off my screen and drop what I want on a custom quick access bar.
Remember: don't let your status as a power user cloud your view of how your grandmother might want to use her computer. There are FAR more 'grandmother' grade users than there are us.
I was a HUGE Apple fan for the early Macs. I totally get what you are saying. But we LOST in the workplace. It was just too slow for the other folks in the office to use (of course, the real death blow was having only a graphics mode to the display so the typing was dreadfully slow-- and the secretaries wouldn't use them- but that's another story).
But I get your point. That's why I phrased my response as I did. I have never done UI/UX testing- maybe the parent has and was sharing his insight.
But if we are all just speculating, I've got to throw out a shout for the other point of view. Yes, too many (how many is too many? I don't know) and it gets to be like using VIM. But two buttons? Seems like it should be ok.
Trust me, I agree that this new ribbon is very cluttered and contains too much visual noise, but in turn I don't mind exposing things visually to the end user. I hate MS Office with the ribbon, but I deal with people all the time who love it. Just let me turn it off :)
Well she no more typical a computer user than you are I would think. I like to see a curve of typical computer users age distribution (but I understand it would be a little skewed if it's hard for the older generations to use computers).
I feel that ribbon is designed for a select group of new users who need that kind of help. And I hope it's easy to disable it. It's fine for Microsoft to use something like this as a default mode as long as power users are able to turn that stuff off.
This is what turns me off on OS X, there is often no way to do certain more advanced things. Or it's hidden so well it requires hours of searching on the web for what plist to modify.
The shortcut for move is Cmd-Option-V, if anyone wants to know.
1. Why?
2. `rm huge-file`
That reminds me of the first few times I tried to learn vim.
Now though, any other editor that's not Vim or Emacs feels like that...
Just double click on one of the tabs.
In a desktop OS, you have a seemingly infinite set of modifiers (Ctrl, Alt, Double click, click, right click, Ctrl + Shift), which are not 'logical' operations like tapping and swiping - they must be learned and remembered.
I'm sure there's a few more buried in there that I haven't discovered. (Like swipe backwards to delete an item from a list)
And now even those are getting out of control:
http://www.apple.com/macosx/whats-new/gestures.html
Pretty soon I'm going to run out of fingers, and these certainly aren't easily discoverable.
This same pattern continues on iOS devices. They don't ever use complicated gestures, certainly not as the only way to accomplish something. The most complicated gesture you need is pinching.
The new iOS 5 has gestures to switch apps and get home, but those are really like keyboard shortcuts since the home button is still there and offers a simpler alternative.
Easy? Maybe for some. I bet the same people who have to be told to right-click also have to be told how to work their bluetooth/wifi connection (and never bother to turn it off to save battery).
But I'll grant you this point if s/easy/possible/
I think that you overstate the importance of turning off wifi and bluetooth. Those are power user options, for sure. When you're trying to conserve battery power, you're trying to streamline how you use the device, which to me, smacks of 'power user'.
The flipside to that argument is that it is ridiculously easy to browse a web site, check your email and play Words with Friends and Angry Birds. These are the things that the majority of people care about... not whether or not a given physical interface is active or not.
And you are right, of course, in that ios allows most people to do the things they most care about very easily-- that's probably the takeaway. If you do that, then, apparently even if the other stuff is hard, people will probably figure out how to do it when they need it. Somehow.
Android devices on the other hand, need constant fiddling. My Droid would barely last a day with everything turned off, and with wifi, etc. turned on, it would die after only about 6 hours.
Disclaimer: I don't own an iOS device, so don't know how intuitive it might or might not be.
The only reason to turn off the cell radio but not the wifi radio is to conserve battery, which again puts you well outside the use case of the typical apple user.
In my experience, this is rarely enforced.
(In fact, I just got off a plane, and the announcement is "electronic devices must be off, not in airplane mode. that's for after we're in the air.")
The actual removal of abstraction (mouse) have made it much easier to use it. This is why my son at 2 can use the ipad and he can't use the mouse and keyboard for the desktop and laptops.
I have no doubt that this UI, though cluttered, will help users out but I question whether this is ultimately the best solution.
ie there's an inductive leap between "I want to delete all files except this one" and "I can select that one file and then invert selection before deleting". At minimum it requires you to know what "invert selection" means. Ordinary users may take a different, more fiddly, path.
I don't know if that's the case here. My intuition says it is. However, in my optimistic heart I hope Microsoft did a bunch of usability testing and determined that ordinary users do grasp an "invert selection" concept more often than not.
That's how design for mass-use user interfaces works, right? By evidence-driven testing, not by what the programmer/designer thinks makes sense? Clings to idealistic belief.
The dangerous button is much easier to find than the fix-it button. One is right there, with your files. The other is someplace else, related by metaphor alone. Once you have selected the recycle bin you then have to search through your very long deleted file list, select the file you want, select another button to restore it (which appears in the same place as a different button existed before selecting the file), and then navigate back to the place you were expecting the file to be. We're talking about users who can't figure out a menu, but they can perform this multi-step task. I can easily see a new computer user screwing this up.
Next time you look at the context menu of a removable drive, see that "Format" is right there with the eject menu item. One should be used every time you use the drive, the other very rarely and only when you're sure. The latter should be removed to a sub-menu under "advanced", or similar.
Myself, I'd make it harder to delete things and a lot easier to find them again.
Or maybe two. One to go from selected file to all other files, and another click to get back.
Selection only comes handy when you will be doing something to several items at once. Thus, the selection function could be turned on via a menu item or a button: it's a totally different operating mode where you click on or drag around the items to select them.
For new users I might agree that they could figure out a right click because everything is new. But for users where everything is familiar ("I've always done it this way"), it gets much harder to break those expected actions.
Second part is about explorer itself. While it might seem like a common utility (even necessary), I find it very rare for a general user to know about it (my wife does not, nor my parents, siblings, their friends,...but my wife's father does). Once they see it, they have no idea what to do. Copy a file? Really, they have no idea.
Spending 2 years in hell doing phone tech support for an ISP after high school was probably the most valuable career experience I've ever had bar none.
Nothing has prepared me for making and selling software to regular people better than this experience. Entire assumptions about how users interact with computers, ones based on my own experience, were rendered useless.
The ways regular people think about technology is endlessly fascinating because it very rarely has anything to do with how I think about technology.
At my day job, we eventually decided to put our development lead as tier-2 tech support because we couldn't get this across. He receives every single piece of support mail we get and is asked to respond to a pretty good percentage of them.
It's been a 2 year, very difficult, education for him.
Experiencing the mind of the typical user day after day has caused some major changes in his UI design philosophy. Don't bury things in menus, limit the number of ways you can do something, walk users through set procedures, etc.
There's a bunch of different approaches to interface design and many of them don't work well. We've all seen the beautiful but hard to use designs made by professional designers, and the control-panel-of-a-spaceship design made by developers.
It seems that what both cases miss out on is spending time working with and understanding the average guy on the street. Or rather, good interface design means spending lots of time optimizing for regular users.
Seconding. Especially before Windows 7 added Explorer as a pinned item by default, the less-technologically-literate persons I know would simply called it "My Computer", and used it in the large-icon, single-paned view. On one occasion while helping a friend find a file, I opened Explorer and switched it to the Details view option. Between that and the folder hierarchy in the left pane, I guess it looked different enough from "My Computer" that my friend was used to and I was given the reaction "Wow, you're really in the guts of the machine, now."
Now the idea that you actually have more problem with experienced users is interesting. I can see that in myself (damn new microwave!). But I still feel like it's no harder to learn, however, than what a bunch of icons are supposed to represent. But once it's shown, then is it really hard for them?
Seems like the problem is one of discoverability, not complexity.
Their old MacOS Finder was clear and simple - my wife would spend hours arranging her work in coloured folders, each of which opened in a window whose shape and position she had chosen, and was meaningful to her. It was a powerful tool that enabled her to arrange and group her work.
Now, both Apple and Microsoft compete with each other over how bad they can make their file system interface. Microsoft wanted to do away with the filesystem in Longhorn, and Apple have actually done so in iOS.
Is this progress??
You're absolutely right. I don't have the citation on me right now, but spatial mode has been found to be easier to grasp for new users in every single test ever. The only reason it was dropped was because (1) Windows Explorer, (2) power users whined about too many open windows and (3) a lot of people got used to URLs opening in the same window thanks to web browsers, so people sought to apply the same principles to file browsers.
Spatial mode used to be default on GNOME for a long time. There, too, it was dropped because of the same reasons.
See also: http://en.wikipedia.org/wiki/Spatial_file_manager and http://www.bytebot.net/geekdocs/spatial-nautilus.html
You can easily have two Finder windows open on the same folder, meaning you lose the immediate recognition that spatial mode gives you. My personal take - they should have two types of Finder window - a spatial "folder contents" window and a folder-browser (probably in column-view) that only shows folders and maybe a preview of the files within.
So you can navigate quickly/enter file-paths in the browser, but to actually use a folder, you enter spatial mode, so you have the instant recognition of where you are.
The problem is that there's no global switch to force Finder in spatial mode coming from anywhere, anytime. This results in a messy affair when suddenly a non-spatial Finder pops up because you never opened that folder directly and previously put it in spatial mode.
Disclaimer: I believe the best UI for a filesystem manager was Windows Explorer 98, the last iteration with perpetual, irrevocable and non exclusive root access, with Norton Commander as its only rival.
From the moment we cared about maintaining our system's safety from the user's "big fingers syndrome", it all went down (starting with hiding file extensions) to the atrocities we now have to deal with. And yes, I put Seven's Explorer in the same basket as Finder and the likes of Nautilus, mostly due to /that/ horrible folder scrolling bug that MS refuses to hotfix.
Wonderful though Linux is, it's applications are not consistent or mature enough to support a totally document-centric UI. Microsoft could achieve that with Office, but they would probably be accused of over-integration, and hit with the anti-trust stick.
All of those actions require knowing how to [delete], [open folders], [drag and drop].
As someone who has done a fair amount of tutoring seniors on basic computer usage, I have a large amount of anecdotal evidence to indicate this is definitely not the case for them. Depending on the person, I would sometimes try to not show them context menus or keyboard shortcuts at all and just teach them how to use the File, Edit, etc. menus.
There are people who just want to learn the correct order of incantations so that they can check their mail and do things with their photos. And that's okay! Trying to show them that that there is more than one way to do a given action often just leads to confusion as they meld them together (right click on Edit..)
I have seen a fair amount of people with a similar approach as well, but my largest body of personal experience comes from the tutoring, which is why I mentioned it.
I have been seeing the same thing with research colleagues.
What a lot of us in IT or related fields do not "get" from normal users is that the way they "see" the icons and pictures in the computer is completely different from what we do. We have a "mental model" of what Word or Excel or Firefox is doing. Some of us have a more accurate and detailed model than others.
But "normal" users only know what they see and what will happen after they do something (either because they have done it before or because we told them, and they trust us). For them, there is no more meaning to "click on the File menu" than if a Scuba diver told you to "check your SPG every 10 minutes".
Apple has learned a lesson here. They are now heavily optimized for ease and comfort of purchase.
(since we're on topic: I'm an MS employee. I do not work on Windows Explorer)
It seems to me that a lot of people here on HN are simply using this issue to talk about how much better they are at using a computer than the ordinary person, who is apparently quite inept. Unless there is convincing evidence that people that incompetent are still a significant fraction of the userbase, we should stop designing desktop software to accommodate people who are not able to master the use of an iPad.
This is the danger with reading too much into simple data - just because 85% of the people do X, it doesn't mean that X is good. Do you expect the data to show that people don't copy paste because its not intuitive? No, in most cases they 'have' to learn it, and figure it out by asking a friend, but they don't enjoy the learning process (and indirectly, resent the platform itself).
Everyone who struggled with the concept of right clicking eventually learnt it - the problem is not that right clicking or context menus are impossible to learn. It's that they're not a natural way of interaction, and should be eliminated whenever possible.
You shouldn't have to learn to use a menu to do what you want, especially when 80% of the time you just need 4 actions.
The simplicity of modifiers (tap, double tap, swipe) is what makes touch platforms like iOS very intuitive. A direct, clickable button ensures that novice users can accomplish simple file management tasks by learning a single modifier (the click).
Editing is also a pain in the ass on it. It is a wonderful os for very simple tasks, but as the complexity grows it is very limiting.
Maybe that's the moral of this thread.
What this may show is that it is mainly experienced users who use Explorer. And based on my personal experience, I believe this to be the case - most people do not know what Explorer is for, let alone how to use it efficiently.
The reason for using the context menu use in my case is that most options are available only from the context menu...e.g. "edit", "extract [from zip] all", etc. and it is only through many years of trial and error that I have developed any efficiency with the context menu - this is because the problem with context menu operations is that they require enough experience to recognize the context and remember what [hidden] commands will be revealed by a right-click.
The advantage of the ribbon is that context menus are made visible when the context is entered, thus allowing less experienced users explore options more easily. Also, the issue with traditional context menus is that they are a mixture of fixed elements [cut, copy, paste, properties] and context specific items [extract all].
Besides touch-friendliness, ribbons have huge benefits in discoverability. People can't use features they don't know exist; ribbons organize features into browsable, meaningful panels so they can be found, related to each other, and used. The article seems to entirely miss this point.
Nobody knows about them for one reason - they are useless.
Screenshot: http://i.imgur.com/5e5xN.jpg
Edit: Vista/7 may not be completely true, but it's certainly that way on my untechnically-minded mother's laptop - probably the result of context (e.g. in a library of pictures) or a setting somewhere.
Personally, that's an command that I never use; not sure how popular it is with the Windows userbase in general.
In XP, there's a folder that you can put folder and program shortcuts in, that will populate the send to menu. In fact, this essentially is my quicklaunch method when using XP. Just put a link to notepad2 in there, and you can view anything in ascii. Rinse and repeat.
It's so useful in fact, that they might have been able to bring it into wider usage, and maintain continuity with older Windows, by adding a context menu such as 'Make me a send to place', which would add a shortcut to the clicked folder or application into the send to menu.
To me on OS X, the Finder sidebar and Dock are the rough equivalent. 90% of my Finder work is selection and dragging to the sidebar, or Dock, the same thing I would use send to on Windows for.
The "send to" email, however: I don't think you can use it with any web-based email, correct? Do people usually have Outlook set up on their machines these days?
There's one more: if you have a bluetooth adapter (or a laptop with embedded support), it shows a 'Send to Bluetooth device'. I find this very useful for sending files to my phone.
But they had to be put there by the user. :)
Methinks that kind of summarizes the issue: Microsoft doesn't seem to realize it's not 1995 anymore. "Beginners" are no longer a big market, and people are more comfortable with "discovering" software interfaces, as proven by the success of web apps, Apple, etcetera.
Things like moving files around directories is black magic to them. Directories are black magic to them. The problem I see with this solution is two-fold:
1. The people who understand this stuff will be comfortable using context menus.
2. The people who don't understand this stuff will be just a stymied by the "move to" being in the ribbon versus being in a never-seen context menu.
However, what I would imagine MS is hoping with this is that the people in category two will gradually slide up to category one (well, more like 1a) because these things are in their face all the time.
Microsoft's solution is more akin to the way animal researchers teach apes to recognize arbitrary symbols. It's a subtle and pernicious form of vendor "lock in", because when you try to move those users away from their comfort zone in Outlook or Windows Explorer, they feel lost.
Personally, I think Microsoft and "people who can't be bothered to learn their tools" deserve each other.
The actual user story is always: find what I'm looking for. Google got it right with GMail and informal searching - screw manual organization. Power users should be able to set up structures, but typical computer folks don't need that.
For me, the problem with the ribbon has been (the times I tried to use Office 2010) that there are some more "advanced" commands (like, inserting a cross-reference to a Figure or Table) which became quite hidden away in the Ribbon. Specially, since in the old toolbar mode, I could add buttons to the actions I used most (I actually have a button for text-to-columns in Excel, or to bring the "insert cross reference" in Word, among others).
From my experience, the ribbon does not give you that ability.
Actually, every time I have to use the ribbon (my institute's laptop has office 2010) I start imaging an addon which "learns" what are the most used commands and configures the "Home" (or another) ribbon tab showing icons to access those commands. Surely, someone must have already thought of that no?
Also, do you realize that the Ribbon is customizable in Office 2010, in the same way toolbars were customizable in Office pre-2007?
This is similar to what MS did with pulldown menus in the pre-Ribbon days. It sounds like a great idea but it turns out to be a terrible one in practice. During the critical "newbie" phase, as a user begins to work with the program, the UI never seems to look the same twice. Tasks that should become reflexive never lose their dependence on the brain. At the same time, more advanced users are left wondering what interesting features they might be missing.
You really, really do not want a UI that changes behind your back, or in ways that aren't explicitly commanded. Resorting to discrete novice / expert modes is a venial sin in UI design, but "personalized menus" is a mortal one. It's about the worst thing you can do, and IMO there's no reason to think it would be any better in a ribbon-oriented model than in a menu-driven one.
(Edit: I do agree that restricting the adaptive menu scheme to a specific ribbon tab might be a more promising approach than monkeying with the structure and layout of the standard tabs.)
Tons of people struggle with things as simple as sending emails, or adding music.
Because of users like this, Microsoft is where it is. Any big revamp, and they'll just get millions of confused customers who suddenly can't make sense of the most basic functionality. It is Microsoft's own doing that they made their users get used to interfaces like this, but it's not as easy as just scraping it and throwing up something new.
It's also easy to forget that Windows has a userbase 10 times its nearest competitor (which is to say this brings in challenges which competitors might not face).
Jesus, the amount of Microsoft-bashing in on this article is insane.
Remember, its not that user's cant remember right clicking, its that they shouldn't have to. Why should you need two different types of clicks, and 2 sub menus to Send a file to a drive, when you can accomplish it with a single click and a single sub-menu (as is demonstrated in the ribbon)
Making the initial learning curve simple will have implications on the overall feel & appeal of the operating system, but this is something that is difficult to quantify with simple software metrics.
Ok, but the file system metaphor with its files and folders is unintuitive. New users get lost or just don't get that metaphor. You won't make anything easier for them by putting bigger buttons into the toolbar when they can't imagine for what those buttons might be used.
Alone the metaphor of "copying" a file is so unintuitive. If my mother wants to take a look at the photos she took with her cam she sure won't think about "copying" them.
My point is: MS is trying to fix the wrong problem. They should think about getting rid of end user facing file systems instead of bolting bigger and brighter buttons onto a horribly user unfriendly application like the explorer.
People who use Windows are, for the most part, not new computer users. More and more the new users go to a Mac, tablet or smartphone.
The point of that article is that people already use hotkeys and context menus. So building a bigger menu and toolbar is crazy.
Secondly, the actions are being moved from the context menu to the ribbon. Most new computer users find it very hard to remember additional, non intuitive actions like right clicking & context menus. Each of these is a 'modifier' that power users are used to, but which make the mental model of file manipulation much harder for beginners to wrap their heads around. They have to remember to apply these modifiers to see if the functions they want exist. Moving the functions into a contextually aware ribbon will make life much easier for these users.
Third, Move, Copy, Delete & Rename occupy the center of the ribbon. These are the most used commands (by far) and rightfully occupy center stage. Power users will call it clutter, but it will be extremely helpful for beginners.
[Disclaimer: MSFT Employee, but I do not work on Windows]