Apple’s new foldable iPhone, the iPhone Duo, has attracted considerable attention, but reports of early display problems have also raised questions about the reliability of this new technology.
How can a sophisticated electronic product experience failures shortly after launch? Are problems like these necessarily caused by manufacturing defects, or could the original design, component tolerances, and reliability testing also play a part?
In episode 354 of China Manufacturing Decoded, Adrian from Sofeast discusses these questions with reliability engineering expert Andrew Amirnovin. Using the reported iPhone Duo problems as a starting point, they explore why complex products are difficult to engineer, how reliability issues can emerge despite extensive testing, and what hardware companies can learn from these challenges.
An important distinction runs throughout their discussion: a product can be manufactured according to specification and pass its initial quality checks, yet still develop problems during normal use. Understanding why requires looking beyond individual components to the design, manufacturing processes, testing, and interaction of the complete system.
Listen to the audio here or on Apple Podcasts, Spotify, Amazon Music, and other podcast platforms.
Table of Contents
Episode Sections
Here’s a summary of the main topics discussed, but listen to the episode for the complete explanations and examples.
Why are complex electronic products more difficult to make reliable?
A conventional smartphone is already a sophisticated electronic product. Introducing a folding mechanism adds an entirely new set of engineering challenges.
Andrew explains that a foldable smartphone brings together moving mechanical components, flexible OLED displays, cables, adhesives, structural supports, and precision assemblies.
These components need to work together repeatedly throughout the product’s expected life.
For example, a flexible display might perform well when tested independently, and the hinge mechanism might also meet its individual specifications. However, when the two are assembled, their interaction introduces additional stresses.
Small differences in dimensions, alignment, or mechanical movement could affect the complete assembly.
This is why engineers need to consider not only whether individual components function correctly, but also how they behave when integrated into the finished product.
The more complex the product, the more opportunities there are for unexpected interactions and potential failure modes.
Why can products pass reliability testing and still fail in customers’ hands?
One of the most interesting questions raised by the reported iPhone Duo problems is how a product developed by a company with substantial engineering resources could still experience early failures.
Andrew explains that reliability testing is essential, but no testing program can guarantee that every possible problem will be discovered.
Engineers use different tests to simulate the stresses a product might experience during its expected life. These may involve repeated mechanical movements, temperature changes, environmental exposure, or extended operation.
However, laboratory testing cannot always reproduce every combination of real-world conditions.
There is also a difference between testing carefully assembled prototypes and testing products manufactured at scale.
A prototype may contain components that have been individually selected, inspected, and assembled under closely controlled conditions. During mass production, manufacturing tolerances, supplier variations, and assembly processes can introduce differences between units.
A design that works reliably in a small number of prototypes may therefore need further validation before it can be manufactured consistently in large quantities.
How can a small component change create a major manufacturing problem?
A particularly useful example comes from Andrew’s previous manufacturing experience involving a display component used in a GoPro product.
He recalls a situation where an alternative display component appeared acceptable and offered a significant cost saving.
However, the replacement was slightly thicker than the original.
Although that difference might appear insignificant, it affected how the display fitted into the product’s assembly and created difficulties that prevented finished units from being shipped until adjustments were made.
The example illustrates why individual component quality is not the same as system-level compatibility.
A component can pass its own inspection requirements but still create problems when combined with other parts.
This is especially important in compact electronic products, where internal clearances may be very small and several components must fit together precisely.
For manufacturers, the lesson is that apparently minor changes to approved components should be assessed for their effect on the complete product.
A lower-cost alternative is not necessarily a suitable replacement simply because it performs the same basic function.
… and more, please listen to the episode in full.
The Last Word…
The reported iPhone Duo problems provide an interesting starting point for understanding the challenges of developing reliable electronic products.
They should not, however, be interpreted as proof that Apple failed to carry out appropriate reliability testing or that a particular design or manufacturing defect has been established.
The broader engineering lessons apply to almost any company developing electronic or electromechanical products.
- Product reliability needs to be considered from the earliest design stages.
Complex assemblies introduce additional risks, particularly when moving parts, electronics, and tightly controlled mechanical tolerances must work together. - Successful prototypes and component inspections do not guarantee that the finished product will perform reliably during mass production.
Manufacturing variation, supplier changes, and interactions between components can introduce problems that were not apparent during initial development. - Reliability testing needs to reflect how customers will actually use the product, including realistic operating conditions and variations between manufactured units.
- When failures do occur, manufacturers should avoid jumping to conclusions.
A structured root cause investigation is essential for understanding whether corrective action is required in the product design, component specifications, supplier management, or manufacturing processes.
Further Reading
- The Design for Reliability Process for Launching Reliable Products — An earlier discussion with Andrew about identifying reliability risks, validating product designs, testing, and investigating failures.
- Every Component Works. So Why Does the Assembled Product Fail? — Why individually successful components can develop problems when integrated into a complete electronic product.
- How Many Prototype Iterations and Safety & Reliability Tests Do We Need for Our New Product? — Understanding the testing and prototype validation activities needed before manufacturing.
- DfX (Design for X): 12 Optimizations for New Products — How designing for reliability, manufacturing, assembly, and other requirements can reduce product development risks.
- How HALT and HASS Can Help Your Product Development Efforts — An introduction to accelerated testing methods used to identify potential product weaknesses.
External sources referenced in the episode:
- iFixit: iPhone Duo Teardown — Technical examination of the device’s internal construction and potential failure mechanisms.
- MacRumors: Apple’s Response to iPhone Duo Display Reports — Background on reported display problems and Apple’s response.
- Additional Foldable Phone Video Reference — Supplementary video reference discussed during episode preparation.
Important note: Neither Adrian nor Andrew has independently examined affected iPhone Duo devices or established the causes of the reported problems. Their discussion of possible design, manufacturing, or testing issues is technical opinion and engineering theory, not verified findings about Apple or its suppliers. The episode uses publicly reported issues to illustrate broader product reliability principles.
