@lapcatsoftware In case you hadn't seen this yet:
https://github.com/StopTheMadness-Pro/
Pretty sure that's not you.
If any Liquid Glass apologist says "It is still possible for the user to do x" then I think the point has been missed. The question is not whether a task is possible… that's too low a bar. The question has always been "How long does the user have to think to accomplish their task?"
If it takes me 1 second to find the close button on the current tab in Safari, that's far too long. The duration to shoot for is <100ms, smaller numbers are better.
This is what I miss about pre-iOS7 interfaces.
I really wish some of people would get shitty eyesight like mine for at least a day or two.
Nothing is more aggravating than UI getting harder and harder to see when your eyesight is not degrading.
It’s infuriating that mere design choices for aesthetic purposes are the reason.
But yet I’m being too loud, too critical, and should just accept it. Nah.
I may have some prism in my glasses as well as bifocals. But I don’t need the accessibility options yet.
Ever since iOS 7 I can't watch Apple's design videos without thinking they are built from a completely incorrect starting premise and goals.
"UI gets out of the way of your content"
"hides when not needed"
"only appears when the user needs them"
The details hardly matter when listening it feels like all of this has completely the wrong goals from the start.
@stroughtonsmith I've always thought that ObjC + AppKit/UIKit were the main reason we were able to make OS X, iOS, an app store, and apps like Safari, Keynote and more. The tech wasn't perfect, but it was made for real work.
What was needed was an evolution in languages and frameworks, the next generation of ObjC + AppKit/UIKit, tech that preserved the spirit of great tools for great engineers to build great apps.