Just because you've done something a certain way for 20 years doesn't mean it's the BEST way.
...but it's pretty good evidence that it WORKS and the fact that people are familiar with it is a huge advantage. It should set a very high bar for any argument for change: first, understand the old way, then demonstrate that the new way fixes something that was broken and that it doesn't break anything else.
Chesterton's Fence is the principle that reforms should not be made until the reasoning behind the existing state of affairs is understood. Related: Epistemic Modesty From Chesterton’s 1929 book, The Thing, in the chapter entitled The Drift from Domesticity [1]: > In the matter of reforming...
www.lesswrong.com
I know the article here is based on a rumour and not the horses mouth, but it positively reeks of "form-over-function" and "Chesterton's fence". Starting with the fact that the whole project is called "Solarium" - i.e. everything is glass - i.e. aspiration to a form rather than an aspiration to make things more usable.
Then there's the "inspired by Vision OS" and "consistency" thing. Why? OK, some consistency of function is good - but only where appropriate. Vision OS was designed for AR, so there was a reason for making things transparent and keeping on-screen info to a bare minimum. iOS was designed for phones - there's no need for transparency, and no reason not to fill the screen with information, as long as it's clearly presented and well organised. MacOS is designed for laptops and desktops with at least a 14" screen. Apple sell 32" screens with super-high definition - why would anybody want to use all of those expensive pixels to display lots of translucent empty space?
Not having lots of unnecessary clutter should go without saying, but it's only one of a host of competing constraints: mobile-oriented design has already seen a plague of dumbing down and mystery-meat navigation that has made essential (for some) features hard to discover. Some "clutter" is nececessary clutter.
(I have often been frustrated by "PowerPoint" syderome - you demonstrate a new design for a desktop app on a data projector and the audience immediately start complaining that there is too much on the screen... which would be true
if it were a design for a PowerPoint slide that had to get 3 bullet points across in 10 seconds. Of course, in the next breath they start asking for more and more features to be added... but that's the challenge of designing UIs...)
Then there's how the UI works. WatchOS is controlled by a minute touchscreen, barely big enough for multi-touch, and "smart crown". iOS is controlled entirely by a (reasonably large) multi-touch screen and MacOS is controlled by a trackpad or mouse + on-screen-pointer. Those modes of use have
very different affordances (pointers are very precise - so controls can be smaller - and separate pointing from 'clicking' so there is hover functionality allowing pointer shapes or tool tips to indicate what a click will do , touchscreens are far less precise & need larger controls, can't use hover functionality
but have all sorts of multi-touch and gesture possibilities, WatchOS... is always going to need custom UIs. Then VisionOS is controlled by eye-movement and 3D hand gestures which will have a whole different set of affordances...
There are multiple reasons why Microsoft lost the mobile race - but I'm sure that
one of them is that they contrained themselves to try and imitate the Windows UI (while also supporting touch, stylus, keyboard, number-pad, joystick, jog wheel, function buttons...) on a device where it just didn't work well - whereas what-became-iOS was designed from the ground up for a multi-touch-only phone-sized device, rather than as a sort of mini-MacOS. (and Android was designed for Blackberry-like devices until the iPhone came out & it was rapidly re-fitted for touch).
So, yes, consistency where it makes sense, but beyond "use the same icon labels and function names" the UI is best designed for the platform it will be used on.
(Then, of course, we have iPadOS sitting in the big uncanny vally between iOS and MacOS. I think, really, the iPad Pro needs to be a dual-mode device if lots of people are going to use it with a keyboard and pointer).
On the subject of icons - I'm sure I remember - back in the days of "Inside Macintosh" style guides for developers - a recommendation that icons should have unique outlines to help make them visually unique. That baby seems to have been thrown out with the bathwater, with everything being a rounded rectangle(and, frequently, a rounded rectangle with a circular logo).