With Apple I think the problem most comes from their aspiration for a mobile-only world. But they might just be suffering the same problem many (if not most) s

With Apple I think the problem most comes from their aspiration for a mobile-only world. But they might just be suffering the same problem many (if not most) software packages face: The software gets near perfection.... but the organization does not have the capability to process this. They've got a team of developers, and developing on that particular piece of software is what they DO. There are managers of that team, and their career depends much more on keeping their team busy and working on some new thing far more than it relies upon the quality of the software itself. It doesn't look very good if your career seems to 'plateau' and your teams activity is just bugfixes and polishing a stable, usable product. The guy on another team who 'took risks' and radically redesigned the interface or jammed in a few new features that changed the target audience of their application will fare far better, even if their existing target audience has abandoned the application in droves (though they probably won't, as lockin is real). I've never heard of a company which had an endgame - what to do when the software is DONE. I have certainly suffered through many different applications which reached an apex of near-perfection and simply changed direction and went rapidly downhill though.