My actually least favorite feature of modern UIs: doesn't matter if you actually learn to use it, because in two weeks it will change under you with on OTA update. And good luck finding documentation (third party of course) for the new redesign, because you are actually a guinea pig in an A/B test and most users do not have the same experience.
I was talking about being forced to read a manual because the UI wasn't obvious enough when it could have been made obvious without making the UI worse e.g. making features more discoverable by taking them out of right-click menus, preferring single click to double click, removing _unnecessary_ jargon, optimising the UI for common workflows, informative tooltips, better onboarding on the first-run, allowing undoing mistakes (vs warning modals or no undo at all), avoiding modals, auto saving/restoring state so you can continue where you left off.
I really think people take for granted how much better UIs do this stuff now because best practices have improved.
"Read the manual" and (as another comment suggests) "no one questions the need to take driving lessons before being able to operate a car" were common sentiments at the time that blamed the user and excused software for being better.
> Because yes, things like a massive WYSIWYG editor is complex. There is no way around that complexity
Obviously I'm not saying to dumb down complex professional software and stick all menu options in hamburger menus. I'm talking about software that casual non-techy people would often use. Complex software is a whole other design challenge.
I would argue that e.g. VS Code has a lot of UI improvements over Visual Studio though.
It would make more sense if you considered some of the better UIs of today, rather than the worst.
We had these things figured out in the late 90s already.
- Menus were single click, and hierarchially organised
- The hierarchy was similar between programs
- Everything was text, no one had to guess what "tiny arrow inside a box" means
- Everything looked the same, because everything used the same widgets
- Common functions were placed in menus that were labeled the same across applications
- Menu-Items were directly labeled with their shortcuts if they had any
- Hover-Tooltips have been a basic widget of GUI libs for ages
Sure, they didn't win any design awards, but they worked. In all their boring, obvious blandness, they worked, and they were easy to use. And that's the most important thing.> removing _unnecessary_ jargon
Please tell me what is "_unnecessary_ jargon" in things like "File", "Edit", "New", "Preferences", "Save As...", "Tools", "Layout" or "Help"?
> I'm talking about software that casual non-techy people would often use.
As am I. These problems plague many many popular apps as well. Where is the account setting? Behind my profile picture? In a sub-hamburger? In the App-Settings? Where is the sub hamburger? Topright, mid-bottom, only visible when the display is in landscape mode? Do I have to swipe the menu in? If so, from which direction and with how many fingers?
That professional complex software is plagued by this as well is a personal gripe for me as a tech person, but these problems are universal.
I agree menus, predictable locations for features, and keyboard shortcuts are great.
Perhaps standards for things like this will settle in over time. When apps now need to have support for touch + trackpads + mouse + keyboard, the web, and multi-platform (Mac, Windows, iOS, Android, Linux), it's really shaken things up and made it much harder to agree and standardise on common patterns.
No, I am comparing what was common then to what's common now.
Granted, the menu structure of apps back then was in large part common, because there was only the desktop, and GUI programming was still in its infancy, so everyone used the same widgets.
And no, I am not saying that everything back then was great. There absolutely were apps with shite interfaces. Only it was a lot harder to justify them.
> Standards for things like this will likely settle in over time.
Some will, but since we made the transition from building interfaces to designing them, agreeing on standards became much much harder.
Because now interfaces are the playground of marketing, brand recognition, product identity and design fads. Even explaining how an app works can be hard, because the person asking me could be in another group in some godamn A/B test and have a different one, even though we use the same App.
> When apps now need to have support for touch + trackpads + mouse + keyboard, mobile/tablet/desktop screens, and multi-platform
That certainly makes it more difficult, and requires careful consideration for different platforms.
So riddle me this: Why was common the reaction of all these different requirements to suddenly pretend everyone is using a phone for everything all the time?
Because that's how many apps and websites now look: Like something designed for a small phone screen and navigation by thumb. I open a website on a 4K monitor with a laser-precision pointing device, and I get an information density comparable to the intergalactic void.
It's very resource intensive and challenging to design multiple interfaces is the obvious answer here. Designing a website with just a few interactions that's accessible, supports mobile and desktop screens, and works in all browsers is already challenging and time consuming enough. Asking for almost a separate interface for different screen sizes and more costs significant resources that many won't have. I'm not saying using a scaled up mobile app for a desktop app is excusable, but having them both be radically different is hard work.
> Because that's how many apps and websites now look: Like something designed for a small phone screen and navigation by thumb. I open a website on a 4K monitor with a laser-precision pointing device, and I get an information density comparable to the intergalactic void.
What websites and apps in particular? I agree it can be a problem but I'm not experiencing this often with my daily apps and websites.
Sure is. Wanna know why? Because there is no unversal standard on how to do it.
And arriving at such a standard is really really difficult, in no small part because of all the "amazing" design ideas I mentioned before, which are not only fast-and-ever-changing, but also don't work well together.
In ye'olde days, the problem was approached from the technical side: Technically, designing graphical interfaces is hard, so here is a constrained system that gives you these well defined methods for doing so. That's what design gets to play with, so that's the standard. It didn't look cool, and didn't lend itself easily to branding etc. but it worked. In fact it worked so well, that we STILL have ALL the UX elements from these days in active use today, and they STILL WORK.
Nowadays, we are in a situation where we try and approach the problem from the other side: Technical limitations basically went away, so everyone is free to design his own stuff, leading to a cambrian explosion of conflicting principles and ideas, including ideas how to standardize and categorize all of it.
If we were able to get this under control and design universal widgets that can automatically adapt to whatever device they are used on, that would be wonderful. And there are amazingly intelligent people who are trying to do that. But all that effort flies out the window the very next time some design studio or company want a nice juicy piece of personal brand recognition and "design" the next-shiny-thing.
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.