Apple repeats a story we've heard before and admits the company is having trouble walking and chewing gum at the same time. This is not the first time.
Back in early 2007, Apple announced that Mac OS X Leopard would be delayed by October. Why? iPhone. Think of it as an all engineering hand on the deck issue because Apple's engineering resources were unable to get the iPhone out the door in time and release a new version of Mac OS X at the same time. Here we are again.
I have long had a picture in my mind that Apple had a few hundred well-paid, skilled engineers and designers and programmers on staff who just walked around the work of various projects and since they can't work with everything At one time, some products will return to other products.
That's exactly what happened in 2007.
While Leopard's features will be complete then, we cannot deliver the quality release that We and our customers expect from us. We are now planning to show developers a near-final version of Leopard at the conference, giving them a beta copy to take home so they can make their final testing and send Leopard in October. We think it will be well worth the wait. Life often presents deviations, and in this case we are sure that we have done the right ones
Translation : We have limited resources and too many high-tech projects to get them out the door at the same time .
Remember all the security issues and issues in MacOS High Sierra and iOS 1
Apple has been criticized too late, both for security issues and for a number of quality issues, as well as how it handles battery issues on older devices … Apple has shaken its iOS software plans for 2018, which Delays some features next year, to put more focus on managing performance and quality issues … Pressure into 2019 is a series of features, including an update of the home screen and car user interface, enhancements to kernel applications such as mail and image capture updates , photo editing and sharing of experiences.
Translation : Apple has found it difficult to go and chew gum at the same time .
Well, the world's most valuable company can't find enough engineering, design and programming talent to make macOS, iOS, tvOS and watchOS the same way the company wants them all to work and work together.
While a renewed focus on quality and performance can ease a little beyond criticism, someone in the team asks if the approach will lead to higher quality. In addition, customers tend to pay for features that are more than security and reliability, which is difficult to assess at the time of purchase.
Such a strategic change should not be surprising given the breadth and breadth of Apple's ever-growing product line, but have we heard of similar issues and adjustments on Google, Microsoft or Samsung, or any of Apple's other competitors? Are we able to see the inner workings of Apple easier and more detailed than competitors?
And most importantly, why can't Apple go chewing gum at the same time?
Think of Apple's situation for a moment. All of the company's products can fit on top of a conference room table. Apple has huge resources spread across the globe. No company has more money on hand that can and should be used to grow engineer, design and programming talent. What does Apple prevent from chewing gum at the same time? Or put another way, make sure your products are shipped with fewer security issues, fewer errors, and yet the watches and whistles are expecting customers.
Name a technology company with more customers than Apple. Samsung? No, Google, Facebook, et al, don't count because you're a user, not a customer. To be fair, Apple consists of many moving parts. But it's Samsung. So is Google, Amazon, Facebook, Microsoft and other technology companies. Nevertheless, a growing number of Apple products release aging vines (Mac mini, iPad mini, Mac Pro, among others), while new products remain defective or delayed altogether.
Yes, for some, walking and chewing gum at the same time can be difficult. But isn't that the opportunity you'd expect from the world's most valuable, cash-rich technology gadget maker?