I think this and many other questionable UI decisions across the industry in recent years is the fallout of the old guard of UI designers having rotated out for younger replacements in the past decade with little transfer of knowledge occurring.
The lack of transfer I don't think is out of unwillingness from the old guard, but rather due to the greenhorns throwing everything that came before their time out without questioning the reasoning behind any of it (Chesterton’s Fence) and assuming that whatever they came up with was superior and better fit for the modern era ("those old principles can't possibly hold, we have touch screens now!").
It's also been made worse by UI design roles having been taken by those with backgrounds in unrelated design disciplines, as well as sites like Dribbble which reward pretty mockups over working products. This leads to overemphasis on the visual aspect of the UI and not enough on its functional and usability aspects.
I think new UI designers might mistakenly think that they are in the fashion industry, when actually they are in the ergonomics engineering industry, or should be.
I don't like it either, but they are in the fashion industry.
Why did the label on my Fig Newtons get redesigned? It's not because it lacked in usability. It's because the company knows that customers respond to visual updates. If something looks the same year after year, lots of people will see it as old and tired. A redesign makes it feel modern and fresh. At least to enough people that it matters.
I had the same experience on a recent trip to The UPS Store. The color scheme was all different from the previous time I shipped a package. I commented to the clerk that they'd redecorated. He said they do it pretty often.
Software has a visual aspect to it, and the same forces are in effect. Part of a UI designer's job is to be on that treadmill. That's probably not what the job should be, but the people who pay their salary want it to be.
You are right but man the new Fig Newton packaging looks just like the store brand fruit cookies what were they thinking?
Well stated, but I will say, it is not impossible to do both.
Tantacrul is my favourite (and, actually, only) example of this. His work with MuseScore, with Audacity, his videos about them, and his takedowns of Sybellius etc. all opened my eyes to the world of designers who do things with hard-nosed analytical thinking, user studies, good principles, and make something useful. Even his little digressions about Paint3D and Ubuntu's Mobile OS are illustrative.
The amount of times I absolutely cringe from super lux UI which clearly a lot of time and energy went into prettifying at the absolute expense of usability and affordances. I love Apple TV but flip to any screen with multiple buttons and not being able to tell which button is selected. Or the Russian Roulette of Youtube trying to select any of the overlayed buttons on the actual video frame. I would 1000% trade shiny for more usablility in 99% of apps.
There is both ux and and graphic design and they both have their place. Saddly far too often one wins out over another instead of finding balance.
Most UX designers seem to come from a graphic design direction, and they generally do a better job than developers - but not as good as the old school people who did research and wrote detailed guides and such.
The two things that pain me the most are:
(1) Clickable elements no longer visually signifying that they're clickable. Words aren't underlined or written in a special font, sometimes the profile avatar is the clickable link to the profile but sometimes the name is, etc.
(2) No more clean, compact directory trees. We used to have high-contrast compact UI design to look through nested ontologies. Now it's rounded-edges card-based, often without trace lines, and barely ever compact. RIP
> No more clean, compact directory trees
Even plain old tables with sortable rearrangeable columns, a staple of all of the traditional desktop UI frameworks, are increasingly falling by the wayside in favor of mobile-style single-column lists with cells consisting of stacks of labels.
It's incredible. And the labels are all turned into pills or chips. Then they don't allow pivoted views of their lists, or if they do allowed pivots it's a visual nightmare.
This is exhausting with web stuff. Every designer wants flat everything, not even so much as underlining links, let alone enough design to actually make it obvious what's a clickable button.
I think it's this cargo cult attempt to tap into what Apple had pre-2010 on the iPod and first iPhone. They're missing that the design leadership and attention to detail was unparalleled at Apple in that era, so they just flatten everything for a streamlined look and miss every signifier Apple put in its UIs in those days
How about on windows, no visible borders just overlapping off-white
Drives me nuts. It makes everything feel like working on a poorly organized desk.
Alan Kay (of Smalltalk fame) has a similar, related explanation: computing is a pop culture with little regard for the past (https://link.springer.com/content/pdf/bbm:978-3-319-90008-7/...). There are thousands, maybe millions, of developers who have little knowledge of the history of our field. I’ve found this true even of graduates from highly-ranked computer science bachelor’s programs. Think of all of the current-day LLM researchers and engineers who have never heard of Minsky, McCarthy, Lisp machines, and other aspects of the history of AI before we learned that attention was all we needed.
It wouldn’t surprise me if Apple’s UI/UX teams are staffed with people who have never heard of Don Norman, Bruce Tognazzini, Bill Atkinson, Andy Hertzfeld, Susan Kare, Larry Tesler, and other pioneering figures who contributed to Apple’s legendary 1980s and 1990s software.
It’s a lack of onboarding and knowledge transfer, combined with an Eternal September of thousands new CS grads being constantly produced annually, who are sadly not being taught enough history of computing at their universities.
My dream as a CS professor is to help rectify this, at least amongst my students.
It’s when people confuse User Experience Design, which is a systemic and architectural discipline, with UI Art, which is an aesthetic discipline. If you have someone who is professionally the latter doing the former job, you get things people think look good but don’t work well.
This isn’t even to knock either: UI artists are essential to making a UI understandable and enjoyable. But people think the skill sets are the same, and they aren’t.
Disclaimer: am a UX Designer.
I had some hilarious experiences by telling people that they did well, now make the same thing again but make it better. I was quite surprised they put up with it many itterations and even more surprised that each round (with few exceptons) was actually better.
> Alan Kay (of Smalltalk fame)
Alan Kay (of Alan Kay fame)
To be fair, the “younger replacements” have typically grown up surrounded with many more user interfaces than their predecessors, and the same is true for much of the audience they’re designing interfaces for.
Aesthetics aside, some of the specific guidance from the past is simply not as crucial as it used to be when most users were very new to smartphones or personal computers.
>> This leads to overemphasis on the visual aspect of the UI and not enough on its functional and usability aspects.
Accessibility has been left in the dustbin as well. You go to all these sites extolling these beautiful, innovative sites and they're completely useless with a keyboard or screen reader.
Or if you have any sort of non-correctable visual impairment. I'm sighted but recently I had actually been thinking of learning better how to use a screen reader because I genuinely struggle to visually parse a lot of modern UI design. The big move toward flat designs, but with everyone choosing their own idiosyncratic special snowflake way of doing it, leaves very little visual redundancy for people to use as a fallback. Sad to hear that it might not be the solution either.
Also, holy hell, this obsession with huge swathes of negative space is a disaster for anyone who needs to zoom the page for readability. I'm here to see content, not an homage to the backrooms.
We can also lay some blame at Agile's feet. I've seen UX and UI designers genuinely struggle to fit their work into the sprint treadmill. 2 weeks' notice is not enough time to do any sort of serious usability design study.
The move toward fullstack developers, too. When everybody is a jack of all trades, nobody is a master of anything. Least of all UI design, which isn't worth thinking too much about because it's the least likely potential subject of pushback during code review.
> We can also lay some blame at Agile's feet. I've seen UX and UI designers genuinely struggle to fit their work into the sprint treadmill. 2 weeks' notice is not enough time to do any sort of serious usability design study.
Windows 95 significantly overhauled the desktop GUI metaphor, in a way that is still the skeletal structure of desktops today.
Its U/I design since Windows 3.11 came about because of agile, not in spite of it. https://socket3.wordpress.com/2018/02/03/designing-windows-9...
> We recognized that we needed much more opportunity to create a design, try it out with users (perhaps comparing it to other designs), make changes, and gather more user feedback. Our desire to abandon the waterfall model and opt for iterative design fortunately followed similar efforts in other areas of the company, so we had concrete examples of its benefits and feasibility.
You're right that you can't go start to finish on a design in a single 2-week sprint. But that's why you have a repeating series of sprints, you're not supposed to go from start to finish in a single sprint.
The Windows 95 team always had a shippable OS to demo internally to devs, QA, beta testers and users invited by the UX designers for usability testing. Just because you demo something to the product owner does not require that you then release the result immediately to end users. Decouple development from deployment and from release and you'll find agile methods can work just fine.
Perhaps instead of Agile I should have said "What Agile became in the 21st century." I know how Scrum is supposed to work. I just haven't seen anyone actually do it that way since about 2013.
I don't think you can credit Windows 95 to agile when the agile manifesto was first published in 2001 and the whole sprint nonsense didn't start until sometime later. Iterative development goes back to at least the 80s and doesn't require "scrum masters", "sprints", or "t-shirt sizes".
> I don't think you can credit Windows 95 to agile when the agile manifesto was first published in 2001 and the whole sprint nonsense didn't start until sometime later.
Agile manifesto coined a term for things that already existed. It didn’t create it from scratch, nor did it claim to. But W95 did employ methods we would call agile methods today.
I do think that they were right, though, to point out that the practices already existed and that they aren’t inherently at odds with, and ideally support, good UI design. That’s not the part I intended to criticize; it was the modern tendency to discard iterative design and instead just treat sprints a series of immutable milestones with fixed deadlines, except the scope is fixed in a just-in-time manner. But it’s on me for not stating that more clearly.
When the end of a sprint is a hard cutoff point for tasks, agile is done wrong. Just carry unfinished work over - it won't go away, anyway.
I think the trick here is to not co-mingle the development of UI toolkits and the software built with them. Agile works fine if the UI framework itself is its own project with its own lifecycle, suitably long sprints, etc.
This goes against the pattern that's most often observed in the past decade of every product hand-rolling its UI from scratch, though.
I've worked at companies where to save a few thousands € to not buy a Qt license, they'd basically pay 50x more to have a bad copy of it that was also much slower due to using electron.
We let the wrong sort of designers do the design. The designers that simultaneously made changes under the guise of "UX" just sort of made it up as they went along without any basis in reality. That's how we got stuck with the hamburger menu.
FYI it’s Chesterton’s Fence, named after writer G. K. Chesterton.
Fixed, thanks!
> I think this and many other questionable UI decisions across the industry in recent years is the fallout of the old guard of UI designers having rotated out for younger replacements in the past decade with little transfer of knowledge occurring.
Not sure about that, given that John Gruber specifically lays the blame for a slew of recent shitty Apple design decisions on Alan Dye (cough liquid glass cough), and also the reversal of these shitty design decisions on changes made when Dye jumped ship for Meta. Gruber also says the Apple design team is much happier after Dye's departure.
Dye must be over 50, so I don't count him as a "younger replacement".