Urgent.News

What's breaking now, across thousands of outlets.

Tech

Too pricey to sell? Apple cuts iPhone 18 Pro orders

Abstract editorial illustration

Apple has reduced orders for iPhone 18 Pro and iPhone 18 Pro Max components by at least 15%, citing higher memory chip costs and price increases as the main factors affecting demand, according to a report by Nikkei Asia. The slowdown has also raised concerns about the prospects of Apple's first foldable smartphone, the iPhone Duo, which will be sold for $1,999 (Rs 2,99,900) in the US and India.

Component orders for October have been cut by the suppliers, reflecting weaker-than-expected demand for the premium models. The report suggests that Apple may make further reductions in November, but it remains unclear if the same fate will befall the foldable iPhone Duo. The demand concerns have put the spotlight on the iPhone Duo, with one source noting that the device's starting price is too high for a smartphone.

Apple has been working with suppliers to improve production yields for the foldable device, but the folding screen and Apple's quality requirements add complexity to manufacturing. The softer demand for the Pro models may also be attributed to Apple's decision to change its launch schedule this year, prioritizing three premium models while pushing the standard iPhone 18 and iPhone Air for a spring 2027 release.

Written by urgent.news from The Economic Times's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 4 other outlets

Read the original at economictimes.indiatimes.com →

More in Tech

Deploying Django on AWS with Zero Downtime

Originally published on the Djangix blog: Deploying Django on AWS with Zero Downtime Zero downtime on a single small server does not require Kubernetes or a second machine.

  • Deploy Django on AWS using blue-green deployment on a single server.
  • Rollback to previous version instantly if new deployment fails, ensuring zero downtime.

Blocked by CORS Policy: Every Console Message and Its Real Fix

Originally published on the Djangix blog: Blocked by CORS Policy: Every Console Message and Its Real Fix That red CORS message in the browser console feels like one error, but the sentence that…

  • CORS errors stem from server-side configuration, not client-side code.
  • Blocked by CORS Policy indicates mismatched origin, triggering blocked request.
  • Pre-flight OPTIONS request reveals server's allowance for specific methods and headers.

More from Friday 9 October →