Curious, what specifially needs fixed? What's broken?
We should never want an interface redesign unless it's focused on fixing something that's broken, and even then those changes should be incremental, since Apple should be starting from a best-in-class platform well-honed from decades of learning.
Any wholesale change to a website or operating system or app is either:
A) an admission that you really had it completely wrong top-to-bottom before, so look at THIS! (the Microsoft Windows way of doing things and something Apple should never have to do).
B) an admission that you needed something fresh for the sake of something new (iOS7 cough, cough)
For me, I'd like a little of A) in the OS and iOS, semi-wholesale changes to fix certain vague and poor interface elements forced into practice by iOS7 and Yosemite and clinging on today, and which haven't been slowly reversed/fixed like some interface elements have been fixed over time (after Jony was booted)!
🥰 Pleasing to the eye. Never fails to impress. I miss the old Apple website in 2008. Simpler times!
View attachment 2155045
Boring, lifeless. No risks were taken.
No, those are not the only reasons why product design decisions are made.
They aren't the only reasons, but I contend that most other reasons can be binned into either of those categories.
Given that Apple (used to be) is heralded as the "it just works" kingpin, seamlessly blending function with form, what other major decisions would drive a wholesale interface change that don't fall into function or flash/marketing, where, I contend the focus should always treat function first.
Good function supports good marketing; good marketing needs good (or improved) function.
Good marketing with reduced function is pointless.
This isn’t a wholesale change, albeit it’s a significant one concerning discoverability of product lines.
And most product decisions are not wholesale changes at all, so they don’t really fit into either buckets you’ve established.
Text is fast and efficient. Tiny icons that that are hard to distinguish are not needed in the navigation.Too small, too much text, not enough icons / images
It looks like someone fixed that broken html tag. I don’t see that now. The page looks fine.View attachment 2155085I’m nitpicking, but this is modern Apple in a nutshell.
“> next to the Apple in the corner.
It looks like the interns already fixed it!View attachment 2155085I’m nitpicking, but this is modern Apple in a nutshell.
“> next to the Apple in the corner.
Amen. I can't stand when a page shifts after clicking something and you have to refocus your attention.Oh boy, this redesigned navigation is super annoying (if you use the website like before).
E.g. If you just want to click on any of the main tabs like "Mac" or "Watch", then wait for the page to load, then move your curso to any of the icons below, the moment you reached e.g the "MacBook Pro" icon suddenly the navigation bar expands. Worst case you click and it redirects you somewhere else… Usability nightmare!
.globalnav-flyout-scroll-container {
display: none !important;
}
#globalnav-curtain {
display: none !important;
}
#globalnav {
background: var(--globalnav-background) !important;
}
I much prefer the fly-out navigation, and if this has potential to break other websites, there’s literally zero benefit of using this.This new flyout navigation finally managed to get me so annoyed I needed a way to get rid of it.
I am sure there are better, more foolproof solutions, but here is my quick & dirty way of getting rid of it in Safari.
Paste below code into some text file and save it on your disk, e.g. as SafarCustomCSS.css.
Then go to Safari > Settings > Advanced > Stylesheet. There browse & select your newly created css file on your disk.
CSS:.globalnav-flyout-scroll-container { display: none !important; } #globalnav-curtain { display: none !important; } #globalnav { background: var(--globalnav-background) !important; }
Caveat: as the custom css file will apply to ALL websites opened in Safari, the above snippet may possibly break functionality on other websites as well (though just incase they use same CSS class and ids as mentioned in the code above.)
Well great for you that you like it and thanks for telling me how to use MY computer. 😅I much prefer the fly-out navigation, and if this has potential to break other websites, there’s literally zero benefit of using this.
I don’t know why you hate it but you’d be better off getting used to it instead of intentionally breaking Apple’s website along with other websites.
That behavior does not happen for me on my computer. Are you sure it’s not a bug exhibited by the use of an older version of macOS and Safari? Newer versions of Safari support newer CSS rules and features that aren’t supported on older browser versions and could potentially cause problems like rendering or display issues, or even issues where display elements could accidentally trigger when using said older browser versions.Well great for you that you like it and thanks for telling me how to use MY computer. 😅
I explained few posts above just one of the usability flaws of the new flyover navigation. It’s easily getting in the way of things one may want to click. Eg click on iPhone menu item and then try to click on any of the iPhone icons. Suddenly the flyover will appear out of nowhere and block your click. Possibly even kidnap your click and lead you somewhere else.