There were problems with skeuomorphism, to be sure, but the design communities reaction has been even worse.
Eventually I hope we settle on something between bootstrap 3 and the original OSX visual easements.
One big problem was that UX people never figured out what the correct way to operate a thumb dial with a mouse was.
If you're going to draw that sort of conclusion, you need to support it with a lot more than just a laundry list of stuff like "progress bar animations are more difficult to see" and "drop shadows are lighter."
this. the problem is the functionality is the visual appearance of the system, so they hire visual artists who think in terms of aesthetics, not design engineers who think in terms functionality and easy of use.
the number one example i have is that at one point, they thought it was a good idea to have facetime automatically reduce all system volume when on a call. fine. maybe. but there is no option to turn that "feature" off when it should be a trivial matter to do so. so now, when facetiming with my brother, i have to go get another device or hang up and call him back if we want to share a youtube video or a song or whatever.
Take, for example, the new search interface, where you first type a query, wait a little while it's hitting the search index, and only then get shown a button to choose the search options. Compare it with the old search utility (from the classic Mac OS) where you have both ways (simple and advanced) right from the start. The new way was already a crime unimaginable in classic Mac OS. Yet it happened, and I've just checked it -- it was in v10.4 in 2005.
Cultures die slowly, so the wrong turn has probably happened much earlier than the author thinks.
Steve Jobs warned about having "bozos" in a company. Perhaps there are just too many of them working at Apple now that Steve isn't around to fire a few every so often?
http://www.forbes.com/sites/ericjackson/2012/01/31/why-every...
Edit: Found something. Here's a research analyst making the same point: http://www.streetinsider.com/Analyst+Comments/Is+Apple+(AAPL...
I have to say that when I read stuff like this it kind of scares me away from trying to become fluent enough in design to practice it, because of where subjectivity seems to hide. I think I understand the principles of contrast, hierarchy, balance, scale, feedback, etc. in theory, it just seems very difficult to holistically judge a design that may be emphasizing different attributes to achieve these characteristics.
Take the complaint about button weight:
> Where thick, dark borders and arrow glyphs used to bulge the buttons toward one’s eye, the buttons now “weigh” so little that to distinguish them is a chore. The same goes for other buttons throughout OS X.
The borders may appear lighter in the displayed photo, but how can I judge contrast without seeing the contrasted element(s) (i.e. the surface on which the buttons rest, the positioning from other UI elements, etc.). Also in some ways, there seems to be more contrast in the new buttons. For instance, the button shapes seem to contrast from each other by not being cutouts of the same rectangular shape. Perhaps that's the only contrast that's really matters here, since another form of contrast may be in place to distinguish this button group?
Similarly the discussion about drop shadows is difficult for me to grapple with. What are the drop shadows on the dock doing for me? It seems like a drop shadow is useful for distinguishing mutable elements (UI controls) from static content, but the dock only serves to launch applications. As a user of Apple products for years, I'm innately trained to understand this, but perhaps this is untrue of a first time macbook owner? I understand that experimental design to test these kinds of things is very difficult, but perhaps it'd be a more convincing argument with some supporting evidence.
Or take the complaint about feedback with the "New Folder" button in Notes. It's true enough that there's no visual feedback on the button itself, however when you click the button a highlighted text field appears above, waiting for you to enter in the folder name. I sort of understand this complaint, but when I tried to play devil's advocate I came up with the explanation that the feedback was actually drawing attention to the next task I needed to do (i.e. naming the folder) instead of the button itself. Which way of seeing this is valid?
I feel like these kinds of conversations are very interesting and important for making design decisions that benefit the largest number of people, but it seems like the conversation often relies on subjective judgements on design elements that could be argued either way.
