What you need to know
- Tim Cook says Apple is experiencing supply constraints.
- The CEO talked about the issue on today's Q4 earnings call.
- Affected products include the iPhone, iPad, Mac, and Apple Watch.
On today's Q4 earnings call, Tim Cook confirmed that Apple is experiencing widespread supply constraints to meet consumer demand for its products as the company heads into the holiday season.
Kyle McNeely from Jefferies asked Tim Cook and team about the company's supply chain and if it will be able to keep up with consumer demand through the holidays. In response, Tim Cook said that the company is experiencing supply constraints with its new iPhone lineup.
Specifically, Cook said that they are already struggling to keep up with the demand for the new iPhone 12 and iPhone 12 Pro. He also alluded that they may experience the same issues for the upcoming iPhone 12 mini and iPhone 12 Pro Max.
Cook went on to say that the company is also experiencing supply constraints in meeting consumer demand for Mac, iPad, and Apple Watch. He stressed that Apple is "working really, really hard to remedy those as quickly as we can."
If you'd like to learn more about today's earnings call, you can read the full transcript.
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.