Skip to content(if available)orjump to list(if available)

The Decline of Usability: Revisited (2023)

puttycat

I recently cancelled my Spotify subscription because I just simply can't find my way around the app anymore. This is not an exaggeration—I really don't know anymore how to do basic stuff like getting to an album from a song (without going through a series of obscure right clicks).

I'm 38 and have used computers since I was 5.

Reasoning

Spotify just made the 'brilliant' decision to remove the "Add this song to the playlist" button. Now to add songs that Spotify itself recommends based on the playlist you're listening to you have to, right-click the name, select "Add to playlist", scroll to find the playlist you're currently listening to and select it. Before there was a single button to do this.

But at least I got more whitespace on my screen now...

isoprophlex

But why would you want to do that!? All you need is the section with algorithmic suggestions. You're clearly using it wrong.

Analemma_

Spotify’s ultimate goal is to move you completely away from listening to recordings from actual artists, and instead listening to a stream of 100% AI-generated slop that they don’t need to pay any royalties on.

Letting you go from a song you like to its respective album (or really, doing any navigation other than “start/pause this algorithmic playlist”) is counterproductive to that goal and so needs to be disallowed, or at least made as difficult as it can be.

zzo38computer

I think they make valid points (they really do describe the problems with many modern UI that I see, and that many older ones are much better), but they did miss a few things, such as:

- Having keyboard commands is helpful.

- Good documentation is very helpful; a program is understandable if it is documented.

- Some of the difficulty seems to be due to the programming environments and libraries that are used for making these programs; due to badly designed UI libraries and programming environments, the result will also be bad. However, this is not the only thing that can cause these problems.

- On a computer it should also be helpful that the operator is able to make other external programs and can interact with them too, with your software. Command-line programs, user configuration settings, API, etc, can also be helpful in doing this.

layer8

> Having keyboard commands is helpful.

Not just having keyboard commands, but using standard ways to make them discoverable, such as by tooltips, menu item annotations, and underlined characters in labels.

Another aspect in today’s UIs is that they often introduce latency in operations (due to network communication, among other things) while not buffering keystrokes accordingly, which makes it borderline impossible to press memorized sequences of keyboard shortcuts in quick succession, because you always have to double-check that the application is in the right state to receive the next keyboard shortcut. That goes against developing muscle memory for frequently performed operations, and forces a conscious back and forth and constant ascertaining that the command was correctly received by the application, instead of being able to blindly trust it and thereby reduce cognitive overhead.

padjo

I’ve dealt with bug reports where users turned out to be completely unaware that they could scroll an area of UI, but yet we continued the war on scroll bars. I thought that users literally not being able to use the product trumped aesthetics but the Jonny Ive inspired minimalism over functionality won out.

mcswell

One other gripe that I have with modern UIs, which I didn't see mentioned (but which I might just have read past) is the scattering of controls in different places. Many are, of course, across the top in either a real menu or (yuck) a "ribbon", but others are down at the bottom, or along one side or the other of an app's window.

My recollection is that MsWord is particularly bad at this, but since I no longer have it installed (one reason is exactly this!), I can't show it.

But I do have Ms's Visual Studio Code on-screen. There is (thankfully) a real menu, with File, Edit, View and Help (the latter no longer exists on most Microsoft products). I happen to have a terminal open; it has six mostly indecipherable icons across the top of its pane. All the panes--the terminal, the file edit panes, and the "bar" at the right-hand side, have a '...', which seems to be the equivalent of a hamburger menu for that pane. Finally, the status bar down at the bottom of the window has still more indecipherable icons near the left end, and a few info things near the right end, some of which are controls ("Select Interpreter", inexplicably highlighted in brown with yet another icon), and some of which appear to be just info (line and column)--except these at the bottom of the window turn out to pull down a special menu item at the top of the window. For example, the control labeled "Ln and Col" (the latter means the character within the line, not the column in a tab-delimited file) pulls down a menu item that allows you to go to a particular line (but not a particular "column").

crooked-v

The whole point of the Office ribbon was to consolidate controls, because they were at the point where most of their feature requests were for things that already existed but people were completely unaware of on account of every menu and toolbar having 80 million items.

SoftTalker

So instead they moved every feature into 80 million ribbon items, most which are not visible.

mvdtnz

Firefox is a big offender here. Every single interactable UI element is at the top of the window, until you press Ctrl+F and for whatever reason some asshole at Mozilla decided that the Find on Page UI should go to the bottom of the window. Absolutely cooked.

mrob

I don't see a problem with that. If you are using the find in page feature then you are very likely going to type something. Your hands are already on the keyboard. The fact that you said "press Ctrl+F" instead of clicking the menus is evidence for this. All the options are best accessed with keyboard shortcuts, so Fitt's law is not relevant.

However, I just noticed one big UI flaw in this interface. The keyboard shortcuts for finding the next and previous occurrences of the search phrase (enter and shift-enter respectively) are not easily discoverable. They ought to be mentioned in the tooltips for those buttons.

EDIT: And another problem: the next and previous buttons aren't even correctly marked as buttons. It's worse than the "flat" buttons used elsewhere, it's "stealth flat" buttons that only appear when you mouse over them.

bradley13

Gawd, yes. Modern UIs are far less discoverable, and less usable, than their predecessors.

awinter-py

> What is the "Archive" icon even supposed to depict? The lower part of a printer, with a sheet of paper sticking out?

it's a bankers box (a cardboard box for files) which I guess is not a thing one sees often now? skeuomorphism doesn't work on a digital generation because all the real world touchpoints for information have been replaced by digital

layer8

Those boxes seem to be mostly a US thing, and the author is Swedish (or at least the domain is).

carlosjobim

But then they put some lines on the side for no reason and now it looks like a printed sheet.

thwarted

That's the labeling put on bankers boxes so you know what's in them when they are stacked on shelves.

esafak

> What is the "Archive" icon even supposed to depict?

A labeled archive box. https://kagi.com/images?q=archive+box

This raises the question of the universality of icons. They are contextual to territory and time. Until recently, a diskette was the universal icon for saving. Yet nobody under thirty today has probably ever seen one.

layer8

Yeah, I think “what does this icon depict” is a little beside the point, also considering the mIRC screenshot. BUT, what is important is for icons to be easily re-cognizable by shape AND color, and modern low-contrast monochrome icons fail that, being designed to look as uniform as possible. In the Outlook screenshot, the fact that the labels have the same color as the icons also doesn’t help. Furthermore, the label text size there emphasizes the larger-sized icons, although the text is more informative.

Someone

FTA: Another widespread source of influence was IBM Common User Access from 1987, which among other things introduced […] the ellipsis ("...") to indicate menu choices that opened a dialog window.

I think that the Mac, possibly even the Lisa had that before the CUA. https://andymatuschak.org/files/papers/Apple%20Human%20Inter..., page 23: “A dialog box appears whenever the user chooses a menu item that is followed, in the menus itself, by an ellipsis (…)”

mixmastamyk

CUA definitely built on and incorporated Mac innovations, some which were built on work at Xerox. Motif/CDE also converged on the same conventions. And it was glorious for twenty years or so.

Animats

It's less about the look than the state. The article shows the complexity of Blender menus. But that's not the big problem. For an object to be visible, four things must be turned on. It's hard to figure out which setting is set wrong. Especially when a new release adds something new that has to be turned on.

This is a generic problem in Blender. You can't do something because you're in the wrong state, but nothing tells you that you're in the wrong state.

GNU GIMP has always been much worse than Photoshop in this way. When inserting text, the text is in a default size. If you change the size, and then click on a new insert point, it goes back to the default size. Whether or not the last change has been committed is not obvious, and until it has been committed, many menus and icons do nothing, silently. Selection vs. layers vs. commits are very confusing. Just keeping the dockable menus visible is tough.

skydhash

IMO, Human Interfaces Guidelines should be primarily thought of as a foundational layers, like a standard library for common patterns. But the true driver of UX should always be the domain, be it word processing, 3d modelling, or graphic editing. Instead, we have company branding and oversimplification.

I've moved to Emacs, TUI, and CLI tools to escape the madness, not because they'r e better, but they let you do stuff and are at least stable so you don't have to alter your workflow every quarter.

esafak

You speak of the need for domain-driven UX but you have abandoned domain-specific tools?

skydhash

Most of my needs are related to computer operations, so I just craft small scripts. But I would happily use a professional tool if needs be. Like Intellij or Affinity Designer. The issue is more about smaller utilities and office tools.

mvdtnz

I will truly never understand the mind of people who make decisions like "scroll bars should hide". They are like aliens to me, simply impossible to relate to.

gwern

Crazy how often it backfires, too. I wasted 15 minutes a few weeks ago checking a user report that a PDF I hosted was missing exactly half its pages. Eventually, after walking it through my workflow step by step and it not breaking, I realized that it was simply the PDF viewer hiding the horizontal scrollbar which told you that it was a two-page layout. We had both fallen for it. Thanks, GNOME et al! (╯°□°)╯︵ ┻━┻

(This also illustrates the fallacy with the sibling comment blandly asserting that scrollbars should 'simply be hidden when not necessary'.)

1over137

But thanks to the scrollbars being hidden, you got about 20 pixels more of your pdf! /s

bxparks

Invisible scrollbars is probably the number one reason why I scream at the computer when I have to use Chrome instead of Firefox. At some point, Chrome removed the option to make the scrollbars visible. The UX people are completely insane.

Case in point: I tried to install ChromeOS Flex on one of my laptops. After booting from the USB drive, the installer went through a series of screens. On the 3rd or 4th screen, it would hang and make no progress. I rebooted and re-installed. Same thing. Tried a third time. Same thing.

On the 4th try, I accidentally discovered that the dialog box had an invisible scrollbar. WTF. If I two-finger scrolled on the dialog box after moving the mouse pointer into it, it would reveal some additional text on the bottom which indicated that it was not hanging but doing some work.

After I had finished installing ChromeOS, I discovered ChromeOS has a Settings option to "always display scrollbar", but the Chrome browser completely ignores that flag. Awesome. I blew away ChromeOS Flex on my laptop.

jama211

I’m the same, except the opposite - I don’t understand people who want it there permanently, instead of gracefully hiding when not needed.

I think the lesson here is people have different desires and priorities, and that’s ok.

Reasoning

I don't have a strong preference either way but the argument is the scrollbar isn't just for moving your position on the page but also for communicating to the user where they are on the page. If you hide it you're removing half it's functionality.

layer8

“When not needed” is subjective. It’s okay to have an option to hide them when you prefer that, but we are now at a point where websites and apps are adding HTML-based position indicators and “scroll down to see more” labels because scrollbars have lost the ability to serve that function for most users.

mixmastamyk

Traditional scrollbars always went away when they weren't needed. The problem now is going away when they are.

jll29

Nowadays menus are called "+" or "...".

(Enough said.)

esafak

Hamburgers are like a box of chocolates; you never know what you're gonna get. Because finding the features of your product should be an adventure!