I understand the “Pandora’s box” argument, and I’m not saying Nothing broke its promise. They clearly communicated the support period when Phone (2) was sold, and extending support beyond that would be a bonus, not an obligation.
My argument is that Phone (2) is uniquely positioned in Nothing’s lineup.
It was the company’s last true flagship built around the original Glyph Interface philosophy that established Nothing’s identity. Most devices that followed moved toward different market segments, design directions, and interpretations of the Glyph concept. Phone (2) still combines capable flagship-grade hardware, the full original Glyph Interface, and a strong user base.
That is why I think Nothing could justify treating Phone (2) as an exception and extending it to Android 17, or ideally Android 18.
Yes, other phone owners may ask for the same treatment, but precedent does not automatically mean every device qualifies. Nothing could establish clear criteria: hardware capability, chipset support, technical feasibility, device significance, and long-term user base. CMF Phone 1 being technically capable of running another Android version does not necessarily give it the same strategic significance as Phone (2).
More importantly, supporting Phone (2) longer would send a strong message about Nothing as a brand. This is the device that represented Nothing’s flagship ambitions and carried the Glyph Interface in its most complete form. Keeping it relevant longer would preserve one of the company’s most recognizable products rather than prematurely leaving behind a device that still has capable hardware and remains closely associated with the brand’s original identity.
So, no, I don’t believe Nothing owes Phone (2) users Android 17 or 18. I believe extending support would be a smart exception for an exceptional product—and a meaningful gesture toward the we as Early Adopters who helped establish Nothing as a serious smartphone brand.
