I think they need to decouple major updates from new iPhone releases. Right now, the annual hardware releases are driving software updates. Rather than forcing a major version bump each year, release a minor version that supports the new hardware and release the major version when it's ready. If that tends to be every 18 months, that's fine.
So, in this case, we'd have seen, say, iOS 7.1.3 or 7.2 to support the 6 and 6 Plus. In another few months, when it's really really solid, iOS 8.
Alternatively, size the annual major version updates so they can be done to a higher quality level in only 12 months and don't add/change so much in each major revision.
But anyone remember the new 'system extensions' they would release with every new system pre-OSX?
The problem with less frequent updates is that bugs don't get fixed as quickly, or you have to have a lot of little updates coming out more frequently and then people get inundated with those 'little' updates flying around like mosquitoes...
Having major updates coincide with new product isn't Apple's latest problem. TESTING the damn updates on their new hardware before it leaves the confine IS!
How many people think that heads would have rolled for such a freaking unbelievable mess if it had happened say five years ago.
I've done some software development in my days, and you test and test and test again, you try to find some of the more popular but exotic environments to test in 'Just In Case'...
Sure, it is true that nothing tests like releasing the product to the public, but come on... Having
massive failures on your
new products with the update
you also just released is ridiculous. That's 'junior level' crap. And now Bluetooth is 'broken' on their other 'new technology' innovation, CarPlay?
Really??? This is the kind of crap that kills companies!
Apple doesn't need to slow the updates, they need to TEST the damned updates before they send them out!
The public expects less drama, and more '
WOW!' from a company that used to tout itself as 'Think(ing) Different'...