The first thin I do on MacOS is turn on the scroll bars. Yes, MacOS Has them set as "Only Show When Scrolling" by default, which is probably the most ridiculous setting.
It seems like most people who scroll use touch, wheel, or other non-scroll-bar interfaces, and the scroll bars are just a visual indicator of document size and position while navigating it. I know I do— and have for 20 years unless I was using a shitty laptop without a scrolling input method. Maybe unless I'm scrolling through literally millions of lines of text, which is infrequent enough that I'd prefer to have them hidden and revealable by scrolling a bit.
Not having them take up screen real estate and working with most people's usage styles while being configurable for others is the right decision. The problem is systems and applications that don't let you configure them.
People talk about accessibility and their preferences like they are absolute truths— it's a lot more complex. Not having scroll bars sucks for people that never got comfortable with other scrolling input methods and people who use sight interfaces, for example. They couldn't possibly be less relevant to people who use screen readers, and as an input method rather than an Univision visual indicator, only slightly more relevant to people on phones and tablets. Phone and tablet usage has outpaced regular computer usage for quite some time, and that informs users interaction style. Adding visible UI elements adds cognitive load, and for people who never worked with scroll bars out of necessity, they're just another bulky animated distraction on the screen. Most younger users would probably think them about as useful as an always-visible on-screen keyboard.
I guarantee you— the designers at Apple who chose to hide those scroll bars probably thought more about scrolling more than every one of these commenters combined, and that was before they did formal usability studies.
The days of usability studies are long gone.* It's now change for the sake of change.
Spot the indication that not all settings sections are shown in this screenshot, in all display settings and lighting conditions that your device might be used in.
* Were they ever there? I can't believe this dialog background - https://arstechnica.com/gadgets/2001/10/macosx-10-1/4/ - was the "winner" in any usability study. This was removed in 2003-11 with the release of 10.3.
a) That scroll bar decision was made a long time ago
b) Problems with specific dialog boxes or dynamically created features is evidence of problems with those dialog boxes or dynamically created features. As someone who's worked both as a developer and a designer, often the engineers win.
c) Assuming that these topics are simple enough for off-the-cuff reckonin' to validate or invalidate them are exactly why the engineers shouldn't win when it comes to interface decisions.
Because designers and devs don't want to have to do multiple designs. Everyone's aiming for one design that works for everything. The problem is that such a thing is impossible.
Vollying back your flipness-- This sort of reductive assumption about software design is why companies that need people who aren't developers to actually use their products hire interface designers.
Most employers I've had are all about getting engineers to be everything. Designers, infrastructure, QA, UI/UX, and even product/project managers.. everything.
Sounds like you need new employers. The only people who want that are shortsighted managers who don't care that they know nothing about users' needs, and that's certainly not a universal disposition in the software business.
This has been true of every employer I have ever had. It's true outside of "tech" as well but nearly all of my experience has been as a software engineer.
People are generationally creatures of habit. Newer generations are entering the workforce for whom their first personal computing device was a touchscreen smartphone. With that context in mind, it's not surprising that a "native" responsive experience to them will be mobile centric rather than desktop centric. The market then evolves to cater to the needs of its largest cohorts.
Yes. To engineers, the interface is something you use to interact with software. To users, the interface is the software. When they buy (with money or creepy analytics for marketers) software, they're buying an interface. As anybody in business knows, you're not in the business you think you're in, you're in the business your customers think you're in, and if they expect software to behave in a way it can't, their competitor is a half-inch down the app store results/google listing/etc.
Controls? Regardless of whether or not you like the changes, device usage changes the way people use other devices. What you deem "correct" is not the objective universal truth you think it is. Not knowing that is why almost all FOSS interfaces are an absolute dumpster fire.
Does anyone apply formal usability studies anymore? (not just do them - do they apply the results). I was trained in formal UX long ago, and many UIs today outright violate common rules we learned back then. High contrast was considered important for low vision users even if it looked ugly then. Now most UIs are lower contrast and while they look nicer, they are less usable.
Of course I learned long ago and so I'm willing to accept that what was best practices back then might be wrong given new research that I'm not aware of. However this seems unlikely.
Formal usability testing is still practiced in enterprise, military, and professional products.
From what I've seen from colleagues in the consumer space they've predominantly switched to A/B testing and statistical clickstream/log analyses, though large companies sometimes still do run lab studies for important decisions and to rationalize the giant one-way mirror they installed.
It depends on how big/important/popular of a product you're talking about, but most software that your average joe uses (operating systems, native communication apps, national websites) likely either conduct significant usability testing or largely inform their designs using great usability testing from people like the mozilla foundation and the nielsen norman group. And no-- neither of those organizations have to be perfect for that to be a perfectly valid approach, and if you follow that guidance, you'll never end up with a 'very low contrast' interface.
I go to the store to buy a hammer. I’m a hammer user and I use the hammer.
Or I go to the store and I buy heroin. I’m a heroin user and I use the heroin.
These UIs we speak of, are they hammers, or are they heroin?
Because I’m currently looking at a high contrast screen using a mixture of Unix tools created from the late 60s to yesterday.
I’m looking at an Excel spreadsheet made by a team of lawyers that is in a UI. The lawyers themselves highlighted and handled the contrast of the document. Beyond the table itself, Excel’s menu bar is easy to read for the basic operating needs of a spreadsheet. I mean come on, the pivot table UI is clearly masterful. (If Excel was a native plaintext tabular format and you could pipe stdin/out to the GUI app? Gimme!)
However, a lot of software is basically useless these days. It’s not designed from the beginning to be productive in any shape or form.
Some stoned dance by a junkie under a highway overpass is definitely some kind of expressive art form. How much more productive is the expressive art forms promoted by TikTok, Twitter or Twitch?
There’s clearly a scale at play. I’m as big fan of Twitch as much as I’m a big fan of the Buffalo Bills. I’ve always appreciated the sociological aspects of sports. To add some context to my definition of productivity, I would say that group sporting events are overall productive from a sociological perspective, be it IPL cricket or Fortnite tournaments.
TikTok is clearly and quite obviously towards the junkie dance scale of things.
From an experiential position there was not much of a difference between my observations of a woman filming herself doing a weird little dance on the sidewalk while completely oblivious to the rest of the world and the junky on the next block doing a weird little dance on the sidewalk while completely oblivious to the rest of the world. This basic object-level assessment of the actions that we and others experience with our physical bodies is core to the very notion of “meaning”. The “meaning” is just the stoned dance.
I know of no junkies famous for only being junkies but there are definitely TikTokers famous for only being TikTokers so don’t confuse this for some strict equivalence.
I’m just trying to establish a kind of framework for discussing the relationship between productive UI and productive software tools.
A)Yes. I've been in the software business in some capacity for the better part of 25 years and software usability right now is miles beyond what it used to be. Thinking otherwise is a function of nostalgia.
B) if you're doing dev work, you're probably not entirely cognizant of how different your software selection and usage patterns are than most people's, even for non-dev things.
C) there's a whole lot of interfaces out there and the great ones work so naturally and intuitively that you don't even notice them. Those are the ones for which many assume the design decisions were so obvious that they didn't even need designers. That's so so not true.Look at the most popular user-facing software: web browsers are all obsessed with usability (mozilla actually does some of the best open usability research out there.) Instagram, Tik Tok, Facebook, Twitter, et al... Incredibly clear and usable for their target market. Can't get much higher contrast than you do in email applications and other communication apps. There are tools to guage if your text color/background color/ and text size make for readable text according to the WCAG and I have never had a job, either as a designer or as a developer, where AA compliance wasn't a minimum for all functional elements. Most common user-facing interfaces that regularly use light or white text on colored backgrounds, like the iMessage interface or signal, benefit from OS-level accessibility enhancements like increased text size, which are very commonly used among the people who need them. My non-tech-savvy elderly relatives all knew about them through the setup process on their devices when they first bought them, and never looked back. Looking through every communication or other popular user-facing software package on my Galaxy U22 using a default theme shows nothing even remotely low-contrast.
> the designers at Apple who chose to hide those scroll bars probably thought more about scrolling more than every one of these commenters combined, and that was before they did formal usability studies.
This blind appeal to authority shouldn't convince anyone.
That point is how you justify all your conjecture. Rethink what you wrote because all you're really doing is relying on anecdotes. I can literally say the opposite (I always use the scrollbar for scrolling and everybody I know does too) and we'd have made zero progress.
You haven't actually made an argument worth arguing about. It's devoid of value and it's not a productive addition to the conversation.
And don't bother wasting any more of my time. I don't care. You clearly have nothing to say.
I think you're missing the point. Usability is not prescriptive. You implement what your users have the easiest time using. Touch interfaces change how people interact with interfaces. If you care about usability, you work with people on that and not against them.
I saw those fat candy looking aqua scrollbars in the linked article and I immediately thought how great OS X used to look and work. Truly sad the mess macOS is now.
Not getting it. I mean, if Mac OS lets you configure scroll bars (and I haven't noticed a problem with the defaults so far either) that's much much more than can be said about gnome isn't it? Where gnome theming has gone from black magic in v3 to ... anathema in v4.
> Yes, MacOS Has them set as "Only Show When Scrolling" by default, which is probably the most ridiculous setting.
I have used MacOS every day for 10 years and i've never, except in exceptional circumstances, used the scrollbar to scroll. I don't see anybody in my circle using it. They all have the "Only Show When Scrolling" setting on.
I don't think this is ridiculous and I would enable the setting if turned off by default.
I also spend 99% percent of my time in full-screen mode in safari, vscode or terminal. So the top bar is also hidden by default. I think this is much more focused.
The scroll bar, for me at. least, is also used to gauge how far along in a document I am. So its use is more than just for moving. If I have to find out here I am in a document by scrolling that just means extra effort on my part.
Yes, we should absolutely make everything less accessible in the name of aesthetics. That's made computer interfaces so much better in the past 20 years.
The first thin I do on MacOS is turn on the scroll bars. Yes, MacOS Has them set as "Only Show When Scrolling" by default, which is probably the most ridiculous setting.