I don't think that's quite right. Snow Leopard was a lot of changes to a lot of the OS code base and wasn't great out of the gate, taking multiple dot releases, like all large-scale software updates do, to stabilize and bugfix enough to be "good."
There is no silver bullet, just a lot of lead ones and the answer to Apple's quality problem is to begin baking QA back into the process in a meaningful way after letting it atrophy for the last decade or so.
Hire more humans and rely less on automation. Trust your developers, QA, and user support folks and the feedback they push up the chain of command. Fix bugs as the arise instead of assigning them to "future" or whatever. Don't release features until they're sufficient stable.
This is all basic stuff for a software company, stuff that Apple seems to have forgotten under the leadership of that glorified accountant, Cook.
There is no silver bullet, just a lot of lead ones and the answer to Apple's quality problem is to begin baking QA back into the process in a meaningful way after letting it atrophy for the last decade or so.
Hire more humans and rely less on automation. Trust your developers, QA, and user support folks and the feedback they push up the chain of command. Fix bugs as the arise instead of assigning them to "future" or whatever. Don't release features until they're sufficient stable.
This is all basic stuff for a software company, stuff that Apple seems to have forgotten under the leadership of that glorified accountant, Cook.