Bring Back Idiomatic Design
45 points by fanf
45 points by fanf
Is Apple these days truly a pillar to look up to In terms of UI design and its consistency? (I’m satisfied with hardware)
It's not amazing, but it remains better than most of the alternatives. A few examples:
NSDocument apps on macOS still have a document proxy in the menu bar and you can send a reference to the document by dragging that. Want to attach a document that you're working on to an email? Drag from there to the email compose window. Want to interact with it in the terminal? Drag it to the terminal window. Microsoft Office apps display an icon there but it isn't a file proxy, and that's one of the big reasons their apps feel weird on macOS.NSTextView is a very powerful text editing widget and so nothing except Electron apps and MS Office rolls their own. This means that you have a consistent spell checking dictionary across apps, the same keyboard navigation works, and so on. Command-shift-t toggles it between rich and plain-text editing modes, and that shortcut works in Mail.app and TextEdit, in spite of the fact that they've very different applications (and in any other app that supports both modes).There's a lot they get wrong, but that baseline is something I haven't seen anywhere else.
I'm not the biggest fan of Liquid Glass, but it does feel internally consistent. At least when it isn't bugging out.
The post fails to mention the third reason why these interfaces all look different: branding. Every damn product must use its own set of icons because how else is it gonna develop its "visual identity" to stand out from the competitors? How else are they gonna make sure you're constantly reminded you're using product Foo if it looks like something else?
This, too, is a form of enshittification: caring more about the company's goals than the user's goals. That's our default state of things in the software world now.
These are probably the two best pieces of enterprise software available today.
I’m not sure that means what they think it means. Enterprise software isn’t really defined as software that feels nice to use.
I also absolutely dislike notion because of its propensity towards mess, and for years it had a hitching problem in Firefox where typing and selection would break mid writing and you’d have to refresh the whole application to get typing and selection to work.
Enterprise software isn’t really defined as software that feels nice to use.
Yeah, I use Figma pretty often and it can be a very frustrating experience. Especially when they change how the app behaves for the 10th time already for something that feels less intuitive or against what I want it to do, all the while neglecting a lot of quality of life features found in other apps (I'm pretty frustrated at its Bézier curve editor, no function to set a symmetry axis (counting pixels manually for the 1000th time, ugh...) or not having a perceptual colour picker).
This is, on the whole, a great article and one I agree with. Except:
Frontend developers aren’t wrong to do this.
Yes, they are. Frontend developers are very wrong to use all the Chrome-specific APIs that don't add anything and are just there to make more complexity. Of course, I still believe that native apps should be preferred for things like Figma and Notion; running them in a browser feels weird and wrong to me, even in 2026.
In short, there are few web design idioms because front-end development is moving too quickly. Engineers are concerned with what is possible more than with questions of polish, and rightfully so.
No, that is not right. There is no right here. At least the accessibility laws in the United States are beginning to be enforced with teeth; that should really help cut down on all this mess. No one cares about consistency, screen readers, or best practices until the US DOJ starts handing out million+ dollar fines. Wish the EU would start doing the same and taking this seriously. So far, most of the cases there are focused on government sites, not corporations.
Maybe you don’t know what the REC, TRK, OVR labels in the status bar mean. Then you would benefit from another standard pattern: tooltips on mouseover that tell you more about what that thing is or does.
This would be great, but to my knowledge nobody has figured out an idiomatic way to do tooltips on hover on mobile, which rarely supports hover?
(I put 'rarely', because I believe there was a time when Samsung Note phones supported hover with the stylus.)
I believe some capacitive touchscreens can detect fingers just above the surface, but attempts to use this for tooltips failed because:
Seeing as 'tooltip on hover' is hard to do on mobile, perhaps we could bring back the 'What's This' button? It showed a mouse pointer with a question mark; you'd click the button, and then click the thing you wanted to know about. That'd work fine on touchscreens.
I can't find a screenshot of the button... has anyone else got better search-fu? But here's the pointer-and-question-mark cursor, at least. (Second image, they call it the 'Help Select' cursor.) https://www.axialis.com/tutorials/what-is-a-cursor.html
Prefer what’s easy to understand over what’s visually beautiful.
Yeah if this thing were possible at all, modern web would be much better.
My appeal is to bring back some information density, color and visual excitement. White, grey and a single accent color seems to be about as good as you get, together with acres of whitespace. Some apps on a large mobile phone manage to show a whopping 3 items from a scrolling list at a time.
I just realized that when seeing the screenshot of Microsoft Word in Windows 2000, my only thought was "I want this". That system was so responsive! The only thing that made it slow was the hardware. And it was still faster than many bloated React apps today.
We have really collectively lost the way.
Being forced to use Outlook for work, their web app is a pain. There are keyboard shortcuts, but the app is full of trap. You try to reply to an email, it may scroll down to hide the reply pane for some reason. You are never sure to which email you may answer if you try to answer to a mail in the middle of conversation. You can't stack keyboard shortcuts: you need to wait for each key to trigger its effect before pressing the next one. At any moment, the focus can be stolen by another element. The sole comfort is that Windows user will soon be in the same mess, as Outlook Classic is being deprecated by an Electron version.
Also, Teams and Outlook are two widely different web app for some reason.
There is precisely one good thing about the Outlook web app: It isn't the Outlook Windows app.