> but I personally think people really take for granted that the baseline of usability for many areas has hugely increased over the last 20 years. I disagree.

> but I personally think people really take for granted that the baseline of usability for many areas has hugely increased over the last 20 years. I disagree. What has happened, is that products that could get away with it, have hidden more and more functionality away, usually by shoving it into some god-awful hamburger-menu, or simply removed it, to not "confuse the users". That's not improving, that's removing. And it's fruststrating for every power user, and everytime normal users leave the "happy path" the UI-gurus "designing" such things had in mind. > scary technical language, having to read the manual, Yes, people should try and understand the products they use. If they refuse to do so, then the obvious solution are simplified products, which, granted, are easier to understand, with the tradeoff of lacking functionality. Which is completely fine by the way. Right tool for the job and all that. What isn't fine, is if ALL products start doing that, because then it gets really hard for the people who do read manuals to do their job...because suddenly there are no manuals any more, the language used is over-simplified and non-descriptive, and interface elements are god-knows-where. And sadly, that's exactly where we are now in the software world. Because yes, things like a massive WYSIWYG editor is complex. There is no way around that complexity, not if you want it to have all these bells and whistles it's marketed for having. Yes, things like an email client that people organise their online-identiy around is complex. Yes, applications that people manage their financial lifes with have to be complex. No, an error message saying "Oh noes! Something's not working. Maybe try again later!" under the picture of some sad cartoon character is not helpful for tech support to debug problems. My favorite example, and personal beef of mine? Firewall management software. Because, I think we both can agree that people who's job it is to manage corporate firewalls do read the manuals, and are not scared by technical language. But all my reading and being tech savy gets me absolutely nothing, if the only way to configure that thing is by running a click-marathon through what I can only assume was a modern-art design study gone horribly wrong, and the only documentation available is an old youtube video from 2 versions ago. > as you realise how much knowledge you have to build up to confidently use some software. Here is the thing though: In ye 'olde days, all these scary, techy interfaces looked the same. Once you figured out the menu bar in one application, it was easy to transfer that knowledge elsewhere. Want to save something? "File" menu. Want to change what you're working on? "Edit" menu. Want to change settings? Pretty sure there is a "Settings" or "Preferences" hidden somewhere under "Edit". Nowadays, we have a hamburger button, or a 3-dot button, or a title bar, or a sidebar, or maybe it's one of the phones function buttons, or it's a 2-3-4-finger swipe (the directionality of which is anyones guess). The settings may or may not be under Account, or in the App-Settings, or there might not be any settings at all. The account can be reached helpfully via that gear-icon, or by clicking the profile picture, or by hovering over the profile picture and waiting 0.5sec for the dropdown menu to fly in. Or it's not there at all, because that would be scary to the users, and instead I can change account settings via the non-mobile website on my PC. Or via some other app. Oh, and how wonderful those interfaces are where certain elements only become visible when I flip the phone by 90°.. And this continues ad nauseam. There are no rules, no continuity, no obvious way how something works. Knowing how one app works, doesn't teach me anything about the next one, other than how great those ugly textual menu-bars were in comparison.