The report cited information from three individuals involved in the project. According to the sources, Apple recently “informed engineers and suppliers that it has removed the next-generation iPhone Air from the development roadmap, without providing a new release timeline.”
The iPhone Air 2 was originally scheduled to launch next fall alongside the iPhone 18 Pro/Max and the iPhone Fold. The goal for this model was to be lighter than the current iPhone Air while also featuring a larger-capacity battery.
Additionally, Apple planned to introduce the vapor chamber (VC) cooling system — first used in the iPhone 17 Pro — into the iPhone Air 2. Supply chain rumors also suggest that the iPhone Air 2 might adopt a dual-camera setup.
However, Apple has not completely canceled future versions of the iPhone Air. Some engineering teams and manufacturing partners are still continuing related work. That said, there is currently no confirmed release date, a move that insiders describe as “extremely rare, even unprecedented.”
Sources said Foxconn has “dismantled all but one and a half iPhone Air production lines” and expects to halt production entirely by the end of this month. Another manufacturing partner, Luxshare Precision, ceased production of the device at the end of October.

Use on-chain proofs where independent verification matters

Rights provenance, settlement receipts and portable entitlements are stronger use cases than putting every application event on-chain. The design should choose the smallest verifiable record that solves the trust problem. Account for operational reality.

Networks have fees, confirmation delays and occasional congestion. Products need pending states, retries and reconciliation logic so chain behavior does not leak into confusing user experiences.

Keep governance legible

Even if rules are encoded in smart contracts, creators and fans need plain-language explanations of permissions, payouts and expiry. Machine enforcement and human understanding should describe the same policy. Separate the coordination problem from the blockchain choice.

Before putting a workflow on-chain, define what needs shared verification, what can stay private and which parties do not trust one another enough to rely on a single database. Blockchain adds value when multiple actors need a common record, not simply because an AI feature exists. Identity data, private prompts and raw creator assets can often remain off-chain while hashes, attestations or settlement events provide verifiable coordination.

Design for upgrades and reversibility

Smart contracts and tokenized rights can be difficult to change after deployment. Versioning, pause mechanisms and migration paths should exist before the first production transaction. The system should also define which business rules are truly final and which need correction when refunds, disputes or policy changes occur.

Measure user value rather than transaction count. A large number of on-chain events can increase cost without improving the product. Track whether verifiability reduces disputes, improves portability or creates economic opportunities that users and creators actually use.

Keep sensitive data off the public ledger

Public blockchains are poor places for private fan conversations, biometric source material or detailed creator contracts. Store only the minimum proof needed for verification and keep revocable or sensitive content in systems designed for privacy. Hashes and attestations can prove integrity without publishing the underlying data.

Make wallet UX understandable. Users should know what they are signing and why. Abstract chain details where possible, but never hide the asset, amount, destination or consequence of an irreversible action.

Plan for multiple rails

Creator platforms may need app-store, card and blockchain payments at the same time. Entitlements and business logic should remain portable across rails instead of coupling the product to one network. Practical implementation check.

Before adopting the mechanism described above, define the exact business rule, who controls it and what evidence will show that it worked. Test the failure path as carefully as the successful path, especially when rights, payments or wallet actions are involved. The final system should also document versioning, rollback and the assumptions that may become stale over time. That turns a one-off experiment into an operating model that creators, users and developers can understand.