Apple to replace damaged iPhone Duo screens without explaining fault

What happened

Apple has acknowledged display problems affecting some units of the iPhone Duo, its first foldable iPhone, days after the device went on sale. The company said customers with the issue would be offered replacements, but it did not explain what is causing the fault.

In a statement, Apple said it was aware of a problem affecting the inner display on a small number of iPhone Duo units. Owners who experience display issues were directed to AppleCare for a replacement. The company did not say how many devices were affected.

The acknowledgement follows customer complaints about damaged screens on the newly launched device. Some early buyers reported cracks and display failures within hours of first use. Images shared on Reddit appear to show damage concentrated around the hinge of the inner display, including vertical cracks through the centre and bright lines across the right side of the screen. The National, which first reported the replacement offer, noted these accounts as the context for Apple's response.

Why it matters

Foldable devices put more mechanical stress on a display than a conventional handset, so early faults in a hinge-based design are a product-quality question as much as a support question. For customers who have paid a premium for a first-generation device, the experience of the first few days of ownership shapes whether they trust the product and the brand that sold it.

The case also shows how a company's communication choices can shape the customer journey. Offering a replacement through a clear, named channel gives owners a next step. Withholding the cause leaves them guessing whether a replacement will fix the problem or whether the fault will return. For organisations in any sector that manage physical products, service channels and digital support together, that gap between the remedy and the explanation is where confidence is either rebuilt or lost.

The Renascence take

Most coverage will focus on the hardware fault itself. The more useful lesson is about the moment after a problem becomes public. A replacement offer resolves the individual case, but it does not answer the question every buyer is asking: is this a one-off or a pattern? Silence on cause invites people to fill the gap with their own explanations, usually the worst ones.

Replacement is a transaction; explanation is a relationship. Customers accept a fix far more readily when they understand what went wrong and why it will not happen again. Operators facing a similar fault should set expectations early, describe the affected scope in plain terms, and make the replacement path as frictionless as possible. The aim is to make a faulty first experience feel like a managed exception rather than a broken promise.