Transparent UI components always add noise by nature, especially glass that is intended to be realistic - see all the refractions shown in the keynote.
Aqua was also playful and suggested the same feel but never got in the way of clarity and was beautifully implemented almost feeling revolutionary at the time.
What is on point for VR use cases where this is taken from, unfortunately ruins a desktop or handheld experience.
A massive loss of precision, focus and a big step backwards.
except apple dictates to its fans whats right. i feel apple has already begun a slow process of making them similar;
what im more curious about is how they will improve the settings app (it seems the desktop settings is the worst its been design and flow wise - ive never liked the ios settings design - i do hope they change both of these for the better)
edit: more newlines
Search isn't the most intuitive and obvious way to everyone. Just adding a search function also isn't an excuse to just totally ignore good UX design and information hierarchy.
I've been a sysadmin my entire career, and still do end-user support occasionally. You'd be surprised how few people use the search function, for anything, on their computers. Just opening the windows start menu and showing them they can search there is like black magic to a frighteningly large amount of people.
I've met fellow Mac users that don't even know spotlight exists, and navigate through the OS and every app via mouse and clicking around.
So yeah, just throwing a search box in your app as an excuse for ignoring the experience of navigating it any other way is bad UX design.
I'm staying with family and just handed my 64 year old mother who has never used a Mac my Macbook Pro with the settings app open, and after explaining the concept of default browser in non-leading language (not mentioning the word default), her first thought was to click Display.
When nothing familiar was there her next thought was to click Search and then type in Browser and she made the connection of "Default Browser" to the concept I mentioned immediately.
-
Non-techies are not going to learn the groupings for OS settings any easier than they'll figure out a UX pattern that's been widely accepted for decades: https://www.nngroup.com/articles/search-visible-and-simple/
Of course, who don't know anything about UX tend to assume personal anecdotes map to a much larger sample size than they actually do.
I do find it amusing how disorganized the app has become, and that has become my favorite example.
I find it even more amusing that you think citing search as a primary UI path is your “smoking gun” of good information hierarchy and interface design.
The original settings app had a nondescript "General" label for this same setting: neither tells me to expect a default browser setting.
Overall the old UI was just the current UI with lower information density.
> Search is always available while the app is open, across all menus and functions.
> Therefore no placement or layout can be singled out as better or worse in the Settings app. All possible hierarchies or arrangements are equal.
> I unroll my Apple UX Researcher Toolkit (contents: blindfold, dart, dartboard, crack pipe), and use it to make my decision: I put the dropdown 3 levels deep under Touch ID, safe in the knowledge that I cannot be criticized, because we've also included a search bar.
It's just bad thinking. Sorry if you're upset I've called it out.
How is that setting spelled? What synonym did they use? Are there multi-work linking hyphens? Will it work with or without them? Is the search fuzzy?
And then localization comes in. Take any translated UI and the search often falls short. Did they translate the setting name? Did they translate it right, or did a google-translate of their localization plist? Will it find the setting if I spell it without accents? Which dialect does it use? Wait I don't know how to say this specific technical work in my native language because nobody actually uses it?
So yeah, please keep categories that make sense.
Actually, even without that, the grouping and the hierarchy don't make sense. Why are some things top-level items and other under "general"? Same for "privacy and security" (I assume that's what it's called in English), for some reason "passwords", "lock screen" and "touch ID and password" are separate top-level items even though they do very much belong to "privacy and security".
The more you look at it, the less sense it makes.
As for the second part, Apple does a remarkable job at updating all of the OS to a new design language. Unlike Windows, which last time I used it, had three different settings panels and UI controls resembling archaeological layers going back to pre XP.
If Apple makes the right platform-specific affordances (which they have a much better chance of doing) I think it can work.
That was a big part of the problem, but the issues with the UI/UX went far beyond that.
For exemple, if you used the search bar in the "start menu" to get something from the control pannel, it would ONLY show the new W8 Metro dialog box that barelly has 1/5th the features and would refuse to show you the real one. It also took multiple years before the metro apps inlcuded in the OS (eg. pdf viewer) could be used in windowed mode (they were fullscreen mode like a video game, without taskbar), even the ipad at the time had better multitasking than the W8 Metro apps.
During that time they also instituted "anti-leak" measures so teams would develop and commit features internally and keep them behind hidden flags that required special permissions from the org to change (via an app they called "red pill"). That means that by the time many teams saw what was happening with the UX in various places in the OS, it was too late to come to consensus.
The entire cycle for the OS was empire building and emperor has no clothing from start to finish. It wasn't until he was ousted that they started to try and pull things back with 8.1 and eventually 10.
I've also noticed a lot of solutions to issues in windows now adopting the usage of power shell one liners as an easy way to fix it, and some times even the only way to change a setting or disable something in the system.
Meanwhile in Linux land with the more recent distros running Gnome I've noticed less and less need to use the command line. Can still be annoying though, but I guess it's the price to pay when you roll the OS of your choice on a system that wasn't really validated for it. (it's amazing it works as well as it does honestly)
The true difference between Windows and other OSes is that the CLI was thought out. I imagine there are still people out there running headless OSes. The UI is optional. Though this isn't the case for macOS, it tries to pretend it is IMO.
What I find wild is that there were internal W8 releases with a proper start menu but they abandon it at some point to fully embrace Metro.
Though Apple has long had a universal design across platforms. Not always in lockstep, but visual traits and behaviours and traits and appearances end up in all of their platforms, which even if it wasn't logical from a design perspective, there is loads of shared code so it's inevitable.
But really a lot of what they showed today reminded me most of Aqua from 25 years ago.
Everyone was keying on the universal design thing, and the seeming importance of "introduces" as if this is a first, and it was such an odd thing for Apple to denote given that they have been using a universal design for a long, long time.
If anything, we saw the iPad make serious roads towards functioning like macOS.