When the ribbons first came out, all the techies I knew groused about them with all the technical reasons that people have mentioned here (which I feel are mostly weak arguments and reek of resistance to change). I wasn’t sure myself.
Until I saw some non-IT people using them for the first time. They LOVED them. They could easily see and get things done way better than before. The people who didn’t have the confidence to poke around in traditional menus had no problem looking through the ribbons and trying things out. In many cases they started doing things that they had no idea existed. The ribbons really opened up these tools for the users, which is really the whole point.
In the case of the ribbons, the techies who rail against them are unequivocally wrong. The arguments against them are the same ones we heard when going from DOS to Windows. It completely loses sight of the point of IT, which is to allow the users to be productive (and no, just because it broke some muscle memory you had, that is not an argument that it broke productivity, that’s an argument that you don’t like change), not to force people to remember random incantations because the greybeard says is “the right way” to do it.
> Until I saw some non-IT people using them for the first time.
It shouldn't be surprising that people who hadn't any prior experience would be fine with ribbons, since it is mainly the people who had experience with the same applications but without ribbons that saw the decrease in their productivity.
> and no, just because it broke some muscle memory you had, that is not an argument that it broke productivity, that’s an argument that you don’t like change
And that is a very good argument, change for the sake of change (or worse, for something inferior) is a waste of time. Building muscle memory is a very good thing when it comes to UIs, the entire point of Windows having a standardized UI in the first place was that people who spent time to learn some program's UI they could apply the same knowledge on another program's UI that they hadn't used before.
Ribbon works against that and as a quick example check File Explorer, WordPad, OneNote (the Windows 10 app) and Windows Paint that all use ribbon-ish interfaces that come with Windows. They all look different, have different tabs and even their default state is different. The closest they have in having a common UI is the File tab and OneNote doesn't even have that.
Ribbon applications not only do not look like other applications but sometimes they do not look like older versions of themselves, since they had to move stuff around to make space for new or changed functionality.
And not all ribbon implementations even behave the same - Windows itself probably comes with 3-4 different implementations that all have little weird differences and that doesn't count all the 3rd party implementations (i think there are more ribbon implementations out there than applications actually using ribbons :-P).
> It shouldn't be surprising that people who hadn't any prior experience
Non-IT people are very definitely NOT people without prior experience — they are the actual Business users of these applications. I would be very surprised to find an IT person who uses Excel and Word more than a business person does. They’re the ones who would have a bigger issue with the ribbon (if there were one), but I’ve never heard a Business user complain about it.
On that last point, it sounds like the Fluent Design team is working hard to merge all the Ribbon implementations. That ongoing effort is interesting to watch because it is going to move everyone's cheese again soon in Word and Excel (and PowerPoint), as the modern Fluent control is the "Simplified Ribbon" control that OneNote today uses (and Outlook optionally; and all the Word/Excel/PowerPoint web apps that people don't pay attention to). (As the Fluent design team decided 2D ribbon layouts were too complex both for implementers and users; the 2007 Office implementations had a ton of work put into UX testing the 2D flows and basically no other Ribbon implementation did.)
It feels ironic/iconic that the Simplified Ribbon just looks like a menu bar and single command bar again, but with the years of insight that "tabs" instead of "menus" gives people a better sense of "space" than traditional pull down menus used to.
Merge all implementations or have all of their programs use the same implementation? I find the former a little weird since there is, e.g., an MFC implementation and then a Win32 implementation (available as a COM object) and AFAIK those two are completely separate (i think the MFC predates the Win32 one and was made by some external company) and "modern apps" use XAML which is completely different from the MFC/Win32 stuff.
Bit of both, I believe. On the one hand, Office as the first Ribbon adopter has to maintain a lot of backwards compatibility (especially for add-ins), and so likely can't move all of its ribbons to a single implementation (though OneNote supposedly is using the WinRT/XAML control). Plus the React Native for Web control (Fabric UI) will always have to be a different from platform-specific implementations.
But the impression I have is that "soon" the MFC/Win32 one and the WPF/XAML ribbon implementations will both be marked deprecated and developers encouraged to use the WinRT/UWP/XAML one (which OneNote supposedly will continue to share moving forward), with Win32 (and WPF) developers expected to use XAML Islands.
(Where "soon" is some release milestone I'm fully not sure about. WinUI 3.0 General Availability, presumably? I think that's still scheduled for "second half 2020".)
At the time I couldn't understand why some people hated it. And I knew how to use the previous version, I was fairly used to it.
But the ribbon made sense. You had the organization of the menus, and discoverability for more uncommon icons since they now had labels. You could always find what you wanted quickly the first time.
Plus, it was collapsible if you needed space, and it worked with the keyboard if you wanted to learn it.
"discoverability for more uncommon icons since they now had labels."
This is like what my father used to say about hitting yourself over the head with a 2-by-4; it felt so good when you stopped. Icons are good if they have a menu label attached. If you have to look for the menu label (which I always do, despite having used MsOffice at work for forever), what do you need the icon for?
"You could always find what you wanted quickly the first time." Wrong. We have now switched to Office 365. In some ways the ribbon is similar, but it's enough different that I'm constantly hunting for something that I sort of knew where to find before. I've resorted to looking for on-line help several times today (you know the kind with the screenshots.) So I'm definitely not finding things quickly the first time. And even after I've used a widget several times, I still don't find it any quicker than I do with the menus in LibreOffice (at home).
I still don't understand what the ribbon provides that customizable toolbars don't. Even after years of using the ribbon, I still don't have the location of even basic things memorized. I used to jump back and forth between excel and a program with toolbars regularly. After setting up the toolbars once, everything was exactly where I wanted it and fit my work flow perfectly. The ribbon in excel on the otherhand I always had to.change tabs to find what i wanted, everything seems kind of arbitrarily laid out, nothing is movable or customizable. I find it limiting by comparison.
Can I group individual elements into custom tool bars that can be docked on any side of the window or be free floating? Can I change the sizes of said tool bars independently to allow larger or smaller buttons for different toolbars? Can I have independent labels for each toolbar?
When something works fine for 99.9% of the users, you have to ask yourself if the things you’re demanding are really necessary.
Is it possible that your workflow is so unique and important that you need something that everyone else is doing just fine without? Sure, maybe — but I doubt it.
I confess, I am a ribbon hater. For three main reasons:
1) It kills muscle memory by changing the size and location of the buttons depending on the window size. And not just the size, but also their shape, appearance and place in dropdown hierarchies (i.e. top level versus behind a dropdown). So even after years of using MS Office with the ribbon I still hunt for commands.
2) It encourages multiple copies of the same command. So instead of learning the one place font-size (e.g.) shows up, you end up hunting every time through 3 or 4 tabs for the place you saw it last.
3) The UI features it was meant to replace was left in the program further increasing the number of areas you have to search through. Looking at Powerpoint as an example, it has the ribbon, formatting panes, traditional formatting dialogs, and the right click quick options menu. There are features available on all of them, but there are also options missing on some but not others. Sometimes I find myself hunting through 3 or 4 of these places for some obscure (e.g. table padding) option.
This opinion is based on using the ribbon in MS Office, which was the first and (I would hope, based on the team's resources) best implementation. Maybe somebody uses the ribbon to its fullest.
I buy their pitch that they studied beginner users and those people had an easier time with the ribbon. But for advanced users, this interface is a nightmare. And can't really be avoided.
I realize the Office team had a very hard task. They can't remove features or some of their 100 million users get mad, and they're making a ton of money so they've got a lot of devs looking to add features, so they've got thousands of features and of course users can't find things.
For a contrasting approach, I think the Keynote app on Mac went a different and easier-to-use route:
1. All the options with no context (e.g. insert new object) are in the top menubar, and the contextual options (e.g. change font color) are in a sidebar. So it's clear where to look for things.
2. Commands are in one place only, so you remember where you should look. (Okay, there's a little bit of duplication as the OS-level font menus are in the menu and the sidebar).
3. The contextual stuff is on the side instead of the top, which works better with the wide screens we use everywhere on desktops these days.
4. Contextual menus options stay the same size and shape and in the same location relative to the content, so you retain your muscle memory.
I hate the ribbon so very much. You stated the many problems with it better than I, but here's why it actively makes me angry:
It takes a lot of space, and seems to always make it very hard to find the things that I need to use. If I have no option but to use the ribbon, my productivity using that software plummets because I so often have to take a lot of time to find the operation that I need. It's incredibly frustrating.
Did you know you can scroll through Ribbon tabs on most (every?) implementation with your scroll wheel? I've been surprised how often that seems to differentiate between people that think finding things in a ribbon is hard/slow versus easy/quick.
Beyond that, have you tried navigating a Ribbon via keyboard? It has also surprised me how many people that liked the old menus because of keyboard navigation don't realize a lot of the same tricks and navigations work exactly the same (Alt, arrow keys, Esc, letters, etc).
> Did you know you can scroll through Ribbon tabs on most (every?) implementation with your scroll wheel?
> Beyond that, have you tried navigating a Ribbon via keyboard?
Yes, to both of those things. Scrolling through the ribbon tabs doesn't address or ease my issue with the ribbon (which is trying to find the operation I want). The problem isn't how quickly I can scroll through the ribbon, but that finding things in it is hard. That said, a good UI solution wouldn't require me to scroll anything like that in the first place.
Keyboard shortcuts let me bypass the ribbon, which is good, but they don't help me with things that I don't do all the time because I won't remember the shortcuts. Aside from the waste of screen space, the ribbon doesn't bother me when doing the routine things.
Not just keyboard shortcuts, but keyboard navigation: you can press-and-release Alt and then "walk" through the Ribbon by keyboard: press arrows to switch tabs, move through sections of commands, drill into dropdowns, then Escape to "go back up" a level.
In terms of finding specific things, every version of the Ribbon in Office has had an accompanying search box (today labeled "Tell me what you want to do", and since the beginning labelled with a light-bulb icon, the last remnant of Clippy iconography, RIP). I still think it would be great if search results had an option like "Show me where to find this on the Ribbon next time", but the icons in the search results are the same as on the Ribbon and sometimes just seeing the icon in the search results can help you find it better the next time.
> you can press-and-release Alt and then "walk" through the Ribbon by keyboard
Ah, I see. That doesn't really address my issues, though.
> every version of the Ribbon in Office has had an accompanying search box
It does? I can't find anything like that in O365 Word at all (I haven't checked the other apps). Regardless, that just underscores how bad the ribbon is -- a search function shouldn't be necessary.
> This opinion is based on using the ribbon in MS Office
I was just about to say the same thing..
Ribbon is good, when done right, but recent iterations of office have just obfuscated things so much that its infuriating.
Microsoft also added a "Tell me what you want to do..." search box, which I think is a clear indication that the current UI is unsatisfactory for a large number of people.
I tried that today. We moved to the new Outlook 365, and it had a bunch of useless (to me) dividers when I sorted by date that said "today" and "yesterday" etc. I wanted to get rid of them, so I asked the search box "how do i omit the today and yesterday dividers". All I got was how to search for emails sent today/ yesterday. I finally found what I wanted using a web search.
(The old Outlook probably had those dividers as well, but I must have found the trick to get rid of them back in 2010.)
I stumbled across this page when I was in early high school, and for someone new to computers in general it was a fascinating read. It taught me that user interface design is something that people actually do for a job and that when done well is delightful to use. Oh, and it set an example of clear, instructive writing with illustrations done right that I think influenced me quite a lot.
Some people don't like the Ribbon, but I love it. As a new user back in the day and a "power user" today, I think it's loads better than the semi-random arrangement of cryptic menus and toolbars we had before.
In my opinion, Microsoft Word 2007 did it best. Later iterations did away with the app button and menu in favour of the obstructive "backstage" menu, and I don't think the flat design does it any favours.
That joke seriously made my day! Where is the global settings/properties menu for Firefox? Photoshop? Eclipse? Premiere Pro? Android Studio?
Between those 5 apps, some of the same category or even same vendor, you can find that one very ubiquitous entry under: Tools, File, Window, Edit, File but there's 4 of them.
Yeah, I think at least half the problem is that among those 5 cross-platform applications, only some of them try to respect the native UI standards on all platforms.
see? that's part of what i was trying to say. you say settings, i think cog, hamburger menu, or even three dots. it's so hard lately because designers want to innovate and make their UI different.
Global settings never standardized in one place for some reason. Everything else is well-organized, but for whatever reason an "Application" menu never became common. It's a shame Microsoft didn't promote such a menu in their own software back in the day.
"the semi-random arrangement of cryptic menus and toolbars we had before." Well, yeah, if some program had a semi-random arrangement of cryptic menus, I guess that was bad. As I remember, Word's' arrangement was quite good and non-cryptic. Now we have instead a semi-random arrangement (afaict) of cryptic icons. (There's a reason the alphabet replaced hieroglyphics.)
> For example, almost any command in a document creating and authoring program could belong in tabs labeled Edit, Format, Tools, Options, Advanced, and More.
Guess what menus Word used?
All of the buttons on the ribbon have labels, except for very common ones on the Home tab. That's one of the main tenets of the ribbon. As compared to toolbars, which made very little use of labels at all.
That must depend on what apps the ribbon appears in. I have no such option in the ones that I use. But on investigation, a couple of them do have a hard-to-find option to remove the ribbon entirely, which was a welcome discovery!
I personally hated the ribbon in Excel, not least because it resulted in changes to all the shortcut keys. That killed productivity significantly for me and my colleagues on my trading desk. We got used to it eventually, but it was not fun in the slightest.
The shortcut keys from older versions of Excel still work. The new ones are easy to find too (hit Alt and they appear, but you can type ahead full speed)
One really positive thing about the Ribbon was that it exposed every command in a Microsoft Office program to a keyboard shortcut. Yes, in earlier versions, most had a keyboard shortcut, but some commands only appeared in toolbars that only showed in certain situations and were never mapped to a keyboard stroke. Now in the ribbon, every button that you can see has a keyboard shortcut.
Did you ever hear the origin story of Ribbons? A smart person at MSFT petitioned Billy G directly about it! It was really a bold move that not a lot of peers supported, and look at what a good move it ended up being. That said, if you can expose a button instead of hiding all the juicy details in a dropdown, you ought'a.
And that's certainly an opinion. The wrong one, as it turns out, but you're as entitled to yours as other people are to theirs. It would be nice to have a choice though, rather than having your opinion forced on others.
I don't have a strong opinion, but also think that mine would be irrelevant anyways -- isn't what matters most here the research they have undoubtedly done to understand how the UI affects their various customers and their needs?
The certainty people often have as to UI design is amusing in light of how successful this line of products has been, as if their small and selfish opinion (or mine!) could somehow be more correct than the millions these guys have invested in getting this right. And not to the problem they or I _personally_ have, but to the problem of shipping a product used by probably billions of people across hundreds of cultures.
I have no doubt that if you (or I!) were in charge of design, guided only by our personal opinions, the product would have completely failed.
This isn't the way UX design works. You have an objective, test it and measure the outcome. You implement a sensible default and work out if a preference to change it is needed.
I was always surprised at the hatred that many (most) "power users" expressed toward the Ribbon design.
To me, the greatest thing about it was that it exposed every Ribbon action with an easily discoverable and repeatable key-sequence. Just hit the Alt key once, and every top level category's hotkey showed up as a hover. Hit that key, and the commands on the ribbon (or next level dropdown) were displayed. "Paste Special", a very common action, became Alt+H+V+S. And you didn't have to do finger twisters like Ctrl+Alt+V (all held down together) to achieve it.
And again, almost EVERY command was available in this way.
Sure, you could create your own hotkeys in versions of Office before this, but the Ribbon brought almost every command within easy reach of those that hate removing their fingers from the keyboard. It wasn't quite VIM (no command mode), but it was a far sight better than anything than had existed before in Office, where most of the advanced UI had been buried away in difficult-to-automate AND navigate (either by keyboard or mouse) modal dialogs.
And by exposing most of the UI to the keyboard, it also enabled easier automation via utilities like AutoHotkey.
All-in-all, it was a power user's dream, but I definitely see how it was harder for a mouse user to develop the muscle memory on the Ribbon vs an icon bar. That, however, I believe is simply a matter of having nearly 100% of the UI be available via the Ribbon, vs. the 20% (or less) of icon bars. The always present trade-off between power and ease-of-use, at least for the mouse user.
FYI, that was how the menus worked in previous versions (Alt-f for the file menu, etc.), so ribbons didn’t expose any new functionality in that regard. In fact, Microsoft bent over backwards to ensure that every old pattern people had used would continue to work exactly the same way.
I thought about mentioning this, but Menus still had a tendency to dead-end into modal dialogs more often than not. A Ribbon command could still end up in a modal, but often times the Ribbon design allowed more functionality to be present in a non-modal way.
I worked for Lotus/IBM when Word Pro was being developed, and they came up with the concept of a non-modal floating property bar (they called it the "Info Bar") that pretty much eliminated modals entirely. While I don't recall whether or not it was very keyboard friendly (I was still a mouse user at the time), it definitely showed me that there was a better way than "modal dialogs everywhere".
When I moved on from IBM and had to use Office, I remember how grating it was every time I ended up in a modal dialog, so this was one more reason I was excited to see the Ribbon come along (more than a decade after Word Pro's Info Bar).
I've never looked to see, but it wouldn't surprise me if some of the MS developers for Office 2007 came from Lotus/IBM, since it was a few years earlier that IBM had really given up the Office Suite fight for good.
I think the hatred wasn't directed at ribbons specifically, but at the tendency of (not only) Microsoft to overhaul the UI of their applications with every major release. Maybe that didn't happen as often with the Office applications (which increased the backlash when it did happen), but with the apps bundled with Windows (e.g. Explorer - not IE, the file manager), you had to find your way again with every new Windows version. That's one of the reasons why under Windows I still use good ol' Total Commander and don't bother with Explorer at all. What Microsoft (and Google, and Apple) don't understand is that for most people, applications are just a tool to get a job done. They don't want the latest and greatest UI, but they get annoyed if they have to re-learn how to do the things they want to do. It's as if the controls on your car would be rearranged every time you got it back from inspection...
"almost EVERY command was available in this way [= via the ribbon]" Surely you're joking, Mr. NotTheDro1ds! Afaict, relatively few of Word's commands are exposed in the ribbon; look for example at the long list of additional commands that can be added to the ribbon (customization). I think, although it would be hard to prove, that more were exposed by the old menus.
It is some power user's dream. There are a huge number of power users who consider it a nightmare, though. Well over half of the people I know who have to use the ribbon range somewhere between disliking it and hating it, because it makes it difficult to find what you need to do.
It makes it easy to find what you need to do. It makes it difficult to apply your knowledge of how things were before it existed. That's a much different problem
But it doesn't make it easy to find what you need to do, because it's almost insanely random.
So I have Word open. When the window is set to one width I get a Styles button and a Styles Pane.
Which do I need to click to remove all styles?
Wrong! The quickest option is the unlabelled Clear All Formatting button above the font/background colour selectors.
I make the window wider. Styles expands to a list of styles - in its own little horizontally scrolling microbox - and the Styles Pane button stays to the right of it.
If I click the Styles Pane, I have the same styles in two spaces on the screen, very close to each other - one in a little scrolling microbox, and the other in a vertical list.
This is nonsensical. It violates any number of established and well-researched design principles.
What's next to the Styles Pane button? "Dictate". Because why not? Most people are going to dictate after styling, and not vice versa.
Meanwhile the box with the font names isn't wide enough to show names properly. Someone decided it would be more useful to fill the ribbon with an expanding horizontally scrolling microbox for styles - which is annoyingly hard to use - than to make the font name box wider, so you can see which font you're using.
And the font size box has some completely useless right padding. Even if you use fractional sizes, or three digit sizes, there's still some useless white space there.
And so on. Is this really the absolute pinnacle of all possible UI designs?
> And so on. Is this really the absolute pinnacle of all possible UI designs?
No, it's just a good UI design. It's easy to pick and choose nonsensical examples like that from any design philosophy. No software perfectly accomplishes every task for every user.
I disagree entirely. I think the ribbon is a great example of terrible UI design because it's clunky, it makes it very hard to find what you need, and it eats up a lot of screen space.
I think that it makes it hard to find what I need to do when what I need to do is something uncommon. This is because it not only hides things, but it changes where it hides things depending on the current state of the application.
It's not a matter of it being different than the other ways. I don't have a problem adapting to new ways, unless the new ways are worse.
I still despise the ribbon. I really would rather just have the old Office 2003 and previous configurable toolbars, that took up a quarter or a third of the vertical space.
The only thing that I hate more than the Ribbon is the way that newer versions of Office products will flash you to a full-screen page when you click on the File menu. All I ever want to do there is do a Save As, and they have shitted up the simple job of popping a save file dialog with all kinds of OneDrive and Sharepoint nonsense.
With all of the images broken/missing (they appear to be linked to a domain that is owned by some domain squatter that is trying to get me to install a skeezy Chrome extension), it's hard to actually compare, and tell what toolbars are enabled on the old version.
But in Word 2003, everything that I ever had on the toolbar would fit into a single row, and Word 2016's ribbon uses the same icons, and is three rows high.
I suggest making use of the Quick Access Toolbar. Move it below the ribbon, and put everything you commonly use on it. Then collapse the ribbon.
This way, common tools are a single click away, and everything else is two clicks away.
Re: the backstage File menu, I agree with you. The app menu in Office 2007 (and the File Explorer) is better because it doesn't change the context—what you're working on is still visible behind the menu. The full-window backstage menu is bewildering.
I look at the change to ribbons through the lens of: "Would they have done it if they had viable competitors?", and I have to think that there's no way MS would have. Everyone would have laughed their way right over to Word Perfect.
Perhaps it makes things easier for new users, but only without competitors where they able to shoe-horn it in for everybody.
Now I use it on a Mac where there are still menus on the top and I can get stuff done. I wish there was an option to enable the menus (and fine, leave the ribbon if you must) on Windows.
When the ribbon was introduced, Microsoft asserted patent rights and asked for a license in order to use it. In fact, you were not allowed to use ribbons in your app without a license.
Since then, license text has mostly disappeared from Microsoft's site. The license page no longer exists. You can't apply for one. I personally last saw text referring to a license requirement in the ribbon MFC samples distributed with Visual Studio. But the question if Microsoft requires a license or asserts patent rights seems to still be open - there has been no statement from Microsoft, and a quick google shows lots of people asking the same question.
The impression I have is that Microsoft let the patent expire at the basic 7 year mark (~2014) as they deemed their UX R&D investment had given them enough lead over competitors in the Office suite space (the primary applications that required a paid license and were not allowed the free license). Around that time Microsoft added Ribbons to Win32 and WPF as freely available controls with no additional license. Fluent Design also seems working to add Ribbon controls to all UI control toolkits with no mention of licensing or patent rights (and seems to be working to move even Office to shared controls).
I'm pretty sure Autodesk use a licensed forum of MS ribbons in a lot of their software; AutoCAD, Inventor etc. But I can't find any references to the specific license agreement...
I've changed the title to reflect that this was originally published around 2007 and I don't think it has changed significantly since. The date 2007 isn't shown on the page, but I first read it around 2008 and it was published for Microsoft Office 2007.
Edit: it may have been published in 2008, since at least one of the linked pages has that date.
I think ribbons are one of the great UX failures of the Microsoft Office suite.
An alternative arrangement of functions are property palettes like they are used in CAD tools, Adobe Photoshop, Open Office, or Apple Pages. There, functions are not globally aranged in ribbons like "Start", "References", but are presented in the context of a selected object.
For example, if I have selected an image, the topmost palette shows properties applicable to an image. In addition, I get tabs with options for the placement of the image in a text frame, and for the page the text frame is located on. Very neat, not at all arbitrary, but reflecting the hierarchy of the objects I am working with.
The below is my experiences based on menus+toolbars vs ribbon bar. Some detail will be subjective but I've tried to add enough detail that can explain why people considered it to be a "bad" UX:
Things were more discoverable in menus and the written title in the menu is often more descriptive than an icon glyph (granted some items in the ribbon bar does also have labels). You then also had the glyphs on the toolbars for power users.
It meant that super frequent tasks you'd learn shortcut keys for. moderately frequent tasks you'd learn the toolbar icon. And infrequent tasks you could still find through the menus.
The idea of the ribbon bar was to make things more discoverable but the issue is having everything presented in one workflow where icons are different sized, some with or without labels and some hidden behind popup menus on the ribbon bar, you make it harder for people to systematically search for something specific that they can't recall where the option is.
Another benefit with the toolbar was customizability. That was great for people to morph the UI around their requirements. This isn't possible with the ribbon bar -- it's a one size fits all approach so for some people it will work well but there are so many people that don't fit well.
> granted some items in the ribbon bar does also have labels
Nearly all ribbon buttons have labels. That's part of the point of ribbons (there's no room for labels on traditional toolbars). The only buttons that don't have labels are well-known ones, all of which I think are on the Home tab.
> Another benefit with the toolbar was customizability.
The ribbon (at least in Office) is far more customisable than traditional menubar+toolbars. Every part of the ribbon can be customised, and the Quick Access Toolbar exists so that the common buttons that you use can be accessible even when the ribbon is collapsed.
I don't know why you dis-like the ribbon, because none of your arguments make sense.
"Every part of the ribbon can be customised" Afaik, that is not true. I tried to do that just today with Outlook; I cannot remove the ribbons (ribbon groups??) that I don't ever use, Send/Receive for example. (When you're connected on a high speed connection, what's the point of that? But you can't get rid of it.) Likewise, in Word I'm pretty sure you can't remove things like the Mailings ribbon. (Mail Merge? How 1980s...)
Also, if I'm not mistaken you can't add commands to any of the existing ribbons; you have to create a new one, even if you only want to add one command.
It's been a long time since I've used a version of Office with menus (sigh...), but IIRC you could change every part of it.
So on the contrary, if my memory serves, the menu was far more customizable than the Office ribbon. (I don't know about toolbars, I never used them.)
...and the stuff that does have labels isn't ordered as systematically as a list. This might not matter to you but for some people, eg those with a particular type of dyslexia, having a UI that feels a little "jumbled up" genuinely does make it significantly harder to quickly glance through a list of items than reading through a menu where everything is stacked.
(before you object to me calling the ribbon bar "jumbled up", I do understand the logic of how frequent tasks are bigger icons etc. I agree there is a hell of a lot of thought and research gone into the ordering and positioning on the ribbon bar. But for quick glancing when searching for irregular tasks it can superficially appear less ordered than a menu does and that made it much harder for me to find things)
> The only buttons that don't have labels are well-known ones, all of which I think are on the Home tab.
...and what if you don't happen to know those items well? As I said before, the "one size fits all" approach of the ribbon bar hurts those in the edge cases.
> The ribbon (at least in Office) is far more customisable than traditional menubar+toolbars
That's not even remotely true. Every aspect of the toolbar and menus was customizable. The same isn't true for the ribbon bar.
> Every part of the ribbon can be customised
Either this is a later development or you're overstating things significantly because I assure you I could not customize much of Word's (nor Excel IIRC) ribbon bar when it was introduced (2007). Believe me, I had tried. At the time I used to write pluggins for Word, Outlook (which didn't yet have the ribbon, that came with a later release of MS Office) and Excel so I definitely wasn't not some 'n00b' who couldn't work his way around the advanced features of an office suite.
Sure you could create new tabs and customize those but you were severely limited in just how much you could alter existing tabs.
> I don't know why you dis-like the ribbon, because none of your arguments make sense.
That's needlessly antagonistic and completely unhelpful.
A stunning disregard to millions, maybe billions of human hours spent learning a menu-based UI of incredibly powerful and feature rich office applications, where ultimately there is no obvious place for an option, feature or toggle; at least offer consistency to make the learning worthwhile.
At the very least preserve the option to keep the old menu. But no, the boardroom was convinced by a shiny presentation. Out with the old, in with the new.
Now, trivial features are easier to find, advanced features are..somewhere else. So you can't discover the advanced features next to the more common ones.
The ribbon was the time when you could start to tell when websites or software products had a new generation of product people taking over and changing things around. You could feel the touch of a designer who hasn't loved or really used the product much. All workflows have become weaker, dumbed down. The important "save as..." icon, where I quickly place the thing somewhere else before I proceed with my fleeting thought, is sabotaged by the delay on the click on "File", the confusion why a menu opens slowly from the left, the hunt downwards to my all-important click. Then, force me into a discussion where to save the file. "Maybe in the cloud as that is what we're selling?" Just no.
Now I won't ever go the extra mile and learn every last feature of an application. Learn it, become fluent, yes. But my learning can only be invested in permanent knowledge. Be it BASH or programming fundamentals. But your UI, no thanks.
I always thought Jobs was prescient to mandate that the menu bar appear as part of the OS chrome on MacOS and not an individual application's chrome like it was on Windows. Always-on menu prevented bored UX folks from EVER removing the menu from the screen. Always active menu has felt clunky on Mac since the advent of multiscreens and very wide screens, but I still appreciate this UX design tenet.
The discoverability heavyweight champ always was and always will be the menu.
I wonder if Jobs ever discussed Always-on menu publicly and contrasted it with Windows' approach.
Can we dispense with the "you hate it because you don't like change" argument yet? It's an easy way to write off other people's opinions and often it's not even close to being true.
It's particularly unlikely to be the reason when we're talking about something that was introduced about 20 years ago because it's not "change" anymore. Everyone is used to it now, and those that still dislike it don't dislike it because "it's new".
It's still new for some of these geeks that were already very experienced with computers around the time when Ribbon was introduced. They've just kept hating it since.
I remember spending 1/2 hour (really!) with my wife looking for the "print" menu entry after installing Office xyz, that first had "ribbons", on her computer.
That's the kind of change that makes you hate computers, and computer programmers.
It's a great example of a series of rational decisions yielding a terrible end result.
Because they started with the wrong question.
IIRC, Jensen Harris said Office (or maybe just Word?) had something like 2,000 (or 20,000?) individual operations (commands plus modifiers). Their initial premise was to better organize and present that dizzying number. Create the perfect visual language taxonomy.
Instead of first trying to figure how to reduce that number.
--
It's been a long, long time since I've used Microsoft products. I used to be quite the Word buff. But you'll get the gist of this example:
Embedding an image within a body of text is a common task. With Word, it just fucking sucks. There's an option for every little thing. Dozens of settings to tweak. And predicting where that image lands, especially with reflow, is more launch and pray than anything rational or deterministic.
But really, there's just 4, maybe 6. different ways any sane person would want that image to be anchored. Just show a preview of those options and let the user pick the result.
If someone needs something more fancy, they should opt to use a desktop publishing app, which is actually built for this kind of work.
But no.
Word has to be all things to all people. So consequently becomes nothing for anyone.
Until I saw some non-IT people using them for the first time. They LOVED them. They could easily see and get things done way better than before. The people who didn’t have the confidence to poke around in traditional menus had no problem looking through the ribbons and trying things out. In many cases they started doing things that they had no idea existed. The ribbons really opened up these tools for the users, which is really the whole point.
In the case of the ribbons, the techies who rail against them are unequivocally wrong. The arguments against them are the same ones we heard when going from DOS to Windows. It completely loses sight of the point of IT, which is to allow the users to be productive (and no, just because it broke some muscle memory you had, that is not an argument that it broke productivity, that’s an argument that you don’t like change), not to force people to remember random incantations because the greybeard says is “the right way” to do it.