'Apple to reduce Face ID accuracy to speed up iPhone X supply'

According to a report by Bloomberg


Tech Desk October 25, 2017
Apple struggles to supply iPhone X on time PHOTO: APPLE

With the iPhone 8 not generating enough demand and the iPhone X poised to fall short of its supply target, Apple looked certain to have a tough winter ahead.

Seems like they have to make some compromises in order to meet their targets. According to a report by Bloomberg, Apple is looking to compromise on its Face ID accuracy in order to speed up manufacturing of its anniversary edition iPhone X.

When the company revealed the device in September, Face ID was seen as the biggest upgrade apart from the design change. It was seen as an upgrade to the Touch ID and the home button that was introduced in iPhone 5S back in 2013.

iPhone X being sued before release over 'animoji' feature

The hardware that emits 30,000 infrared beams onto a face is reportedly the reason for the delay in finishing the product, reports Bloomberg.



The report also claims initial supplier Finisar did not heed Apple’s time constraint issues for manufacturing and finishing of the product which has now resulted in Apple quietly asking the supplier to reduce the precision of the face recognition.

Every iPhone X sold will make Samsung a lot of money

“Over the past decade, we've pushed forward with innovation after innovation, bringing us to this moment, when we can create devices that are far more intelligent, far more capable, and far more creative than ever before” stated Tim Cook, CEO Apple.

We are now not sure if the “creativity” and “innovation” that Cook had claimed to achieve would even look possible.

If this is indeed the case, it will generate a lot of criticism given the high price Apple is charging for the iPhone X and the hype that was built around it.

The company will begin shipping on November 3 unless the device is marred by delays.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ