What you need to know
- The world's manufacturers are battling a global chip shortage.
- A new report says that even Apple and the iPhone may not be safe from its reach.
A new report says that even Apple could be impacted by a global chip shortage because it relies on Qualcomm and Samsung for components in devices like the iPhone 12.
From Nikkei Asia:
Samsung's co-CEO Koh Dong-Jin told shareholders at a meeting on Wednesday that there was a "serious imbalance" in the supply and demand of chips in the IT sector globally, and even Apple may not be safe.
As the report notes:
Earlier this month it was reported that Apple was cutting orders for all of its iPhones by 20% as it revised production estimates made in December. As the report notes, Apple may likely have been pre-empting component shortages, rather than anticipating demand. Whilst Apple might have done enough to avoid any major disruption to its supply chains, this latest report says it might not avoid the impact altogether.
The report follows news that Samsung may forego the release of a Galaxy Note altogether this year because of the shortage.
Stephen Warwick has written about Apple for five years at iMore and previously elsewhere. He covers all of iMore's latest breaking news regarding all of Apple's products and services, both hardware and software. Stephen has interviewed industry experts in a range of fields including finance, litigation, security, and more. He also specializes in curating and reviewing audio hardware and has experience beyond journalism in sound engineering, production, and design.
Before becoming a writer Stephen studied Ancient History at University and also worked at Apple for more than two years. Stephen is also a host on the iMore show, a weekly podcast recorded live that discusses the latest in breaking Apple news, as well as featuring fun trivia about all things Apple.
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.