Stock Mac UI Era Ends as Custom Implementations Go Mainstream
Stock Mac UI loses its edge as popular apps like Things go custom, overturning old assumptions about efficiency.
On Sept. 22, 2026, the developer of NetNewsWire, the Mac RSS reader, published his reflections on stock UI. While crediting the latest macOS for its appearance to a degree, he expressed dissatisfaction with the design of toolbars and sidebars. In coverage via inessential.com via ehamberg on Lobsters, the very commitment to standard components was called into question.
Users have shown — again, I don’t need to prove this — that they don’t think about a stock Mac app vs. custom.
The sentence succinctly captures the reality that users do not think about the distinction between stock and custom. The developer had long believed that adopting stock UI was best. That crumbling premise is at the heart of these reflections.
Why Commitment to Stock UI Is Faltering
The developer described the latest macOS as a visual step forward. Even so, he finds the end result lacking. His assessment of the toolbar appearance is especially harsh.
He also expressed a negative view of full-height sidebars. He said the translucent Liquid Glass-style buttons feel off. We have entered a stage where the stock look is not necessarily preferable.
The developer solicited opinions on his small-scale journal. Using a system linked to Mastodon, he gathered wide responses. He also examined replies to a similar question Isaiah had posed a few days earlier.
The developer said the results were as expected. Many Mac apps that users rate highly for appearance do not use stock UI. He said this fact is already a shared understanding among developers.
Things Shows the Reality of Moving Away
From Stock UI
The to-do management app Things was cited as a concrete example. Things is always named in discussions of design quality. While praised as Mac-like, its implementation departs from the standards.
Its toolbar is not in the fixed position at the top of the screen. It does not use NSToolbar, nor does it support free customization by users. The Liquid Glass-style translucency appears nowhere on the main screens.
It also does not adopt the treatment where content slides under the sidebar. The exception is roughly the toolbar buttons on the settings screen. Only there can Liquid Glass traits be seen.
In other words, visual polish and standards compliance do not coincide. The case of Things symbolizes that gap. Good looks are not determined by the purity of components.
Users Do Not Notice Stock UI
The developer was long an advocate of stock UI. There were two reasons: user familiarity and development effort. He thought following the standards would reduce learning burden and ease maintenance.
But now, he sees both reasons faltering. Users do not choose based on whether an app is stock or custom. They do not take issue with toolbar placement or customizability.
Things, Slack, Craft, OmniFocus and NotePlan were cited as examples. Bear, Reeder, Telegram, Acorn and Tapestry are the same. Obsidian and Audio Hijack also have a strong custom character.
Users understand how to operate all of them without trouble. Almost no users can tell whether they are built with Electron. Many do not even have the concept of Electron.
The developer believes users show no interest even when it is explained. Whether users are familiar with stock UI no longer matters. We have reached a stage where familiarity does not drive choice.
The approach of succeeding with custom implementation rather than existing frameworks overlaps in thinking with the case covered in PSP Counter-Strike Clone Hits 60fps With Rust-Built Engine. Prioritizing optimization even in highly constrained environments leads to results. He sees the same pattern in UI choices for Mac apps.
Why the Assumption of Reduced Development
Effort Collapsed
The remaining issue is the effect of reducing development effort. It was previously assumed that following stock UI made it easier to keep up with yearly OS changes. The expectation was that developers only needed to adjust to each year’s differences.
Reality differed from expectations. NetNewsWire is an app thoroughly committed to stock UI. Even so, last year’s Liquid Glass support proved heavy work.
He says the side that followed the standards rather required more effort. The scope of support was wider than for custom-UI apps. A reversal occurred in which standards compliance did not lead to labor savings.
OS appearance changes affect the foundation. The more standard components you use, the more directly you are hit by changes. Custom-drawn parts can be easier to isolate from the impact.
This experience changed the developer’s view. The formula of adopting standards to save labor has collapsed. Both pillars — familiarity and effort — can be judged to have weakened.
Remaining Impact and Choices for Mac
Development Practices
The developer did not cite Things to criticize it. Rather, he named it as an object of respect. He said he had in the past asked for it to be even more Mac-like.
But he believes the very definition of Mac-like has changed. It is becoming a standard held only by longtime Mac developers. Users’ criteria for evaluation are already elsewhere.
Stock UI will remain an option going forward. It retains advantages in operational consistency and compatibility with assistive technologies. He sees it as still effective for document creation and management uses.
Meanwhile, custom implementation is essential for visual differentiation. It frees up toolbar configuration and translucency adjustments. It makes it easier to put a product’s individuality front and center.
What matters can be assessed as using each approach according to purpose. We are at a stage of choosing components based on product character, not convention. Mac development practices appear to have reached a turning point.
Editorial Opinion
On short-term impact: design guidelines for new Mac apps will be reconsidered over the next 3 to 6 months. Templates premised on adopting standard components will lose their appeal. A mix of custom drawing and standard components will become the default in design. Verification items for OS updates will also need to be restructured for custom UI.
On the long-term view: the very standard for Mac-likeness will be rewritten in 1 to 3 years. Ease of operation, rather than visual consistency, will determine value. Support for assistive technologies and keyboard operation will remain as quality indicators. Developer education will also shift from how to use standard components to how to make design judgments.
On remaining questions: will the spread of custom UI weaken the centripetal force of the OS-side design language. The gap between Apple’s intent and on-the-ground choices may widen. The question is at which layer the consistency users truly seek lies. What should be verified is task completion rates, not familiarity.
References
- “That About Wraps It Up for Stock Mac UI”, by inessential.com via ehamberg — Lobsters, 2026-09-22T19:29:53.000Z (ARR)
- Source URL: https://inessential.com/2026/09/22/that-about-wraps-it-up-for.html
Frequently Asked Questions
- What are the advantages of not using stock Mac UI?
- You can freely decide configuration and translucency treatment, making it easier to express a product's individuality. In some cases it is also easier to isolate the impact of OS appearance changes. If clarity of operation is maintained, user dissatisfaction is said to be unlikely.
- Are there no longer any advantages to using stock UI?
- Advantages remain in operational consistency and compatibility with assistive technologies. It remains effective for routine work such as document management. It is important to judge how to use stock and custom according to purpose.
- Why was Things cited as an example?
- Because while it is highly rated as Mac-like, its implementation departs from the standards. Its toolbar does not use NSToolbar, and the main screens have no Liquid Glass expression. It was taken as a symbol of how polish and standards compliance do not coincide.
Comments