Article illustration 1

A Personal Tale of Device Longevity

The author, who has kept an iPhone X since 2018, shares a frustrating reality: a medical app’s planned obsolescence is forcing a costly upgrade. The phone, which has survived five screen replacements and two battery swaps, had been a reliable companion for work at Riot and daily life until the Dexcom G6 continuous glucose monitor (CGM) app announced it would cease communication with older devices in just 12 days.

“I’ve been hanging onto this little bastard since 2018, the year that I went to work for Riot…” – personal blog, Dec 3 2025

Why Dexcom Is Sunsetting Support

Dexcom’s G6 app, built on iOS, relies on the device’s Bluetooth Low Energy stack and background processing capabilities to stream glucose data in real time. As iOS evolves, newer operating systems introduce stricter background execution limits and updated security frameworks. Maintaining compatibility across multiple iOS versions becomes increasingly expensive, especially for a medical device company that must meet stringent regulatory standards.

“I both do and don’t understand why a medical technology company would sunset support for older devices… I know there’s a burden in supporting all of this older hardware.” – personal blog

From a compliance perspective, each supported OS version requires dedicated testing, certification, and documentation. The cost of this lifecycle maintenance can outweigh the revenue generated by a niche user base on legacy devices.

The Human Impact of Software End‑of‑Life

For patients, an app sunset is more than a convenience loss. The Dexcom G6 app not only displays glucose trends but also shares data with caregivers—here, the author’s husband—through secure cloud sync. Without the app, the patient would have to rely on manual insulin pump readings or a separate base station, both of which reduce real‑time situational awareness.

“I use the Dexcom app to share my blood sugar with my husband's phone, which has real health benefits for me.” – personal blog

The abrupt discontinuation of support can lead to missed readings, delayed insulin dosing, and increased anxiety. In the broader context, this scenario underscores the fragility of digital health ecosystems that depend on continuous software support.

Lessons for Developers and Device Manufacturers

  1. Plan for Medical Device Longevity – Software that interfaces with life‑supporting hardware should adopt a longer support horizon than typical consumer apps. A 5‑year maintenance window is not uncommon in medical device software.
  2. Communicate Early and Transparently – Users should receive advance notice of support sunsets, along with clear migration paths and alternative solutions.
  3. Encourage Hardware‑Independent Data Paths – Providing a standalone base station or web‑based dashboard can mitigate the impact of device obsolescence.
  4. Leverage Modular Architecture – Decoupling core functionality from platform‑specific APIs can reduce the cost of porting to new OS versions.

A Broader Reflection

The author’s experience is a microcosm of a larger trend: as operating systems evolve, the pressure on software vendors—especially those in regulated sectors—to retire legacy support intensifies. For patients, the stakes are high; for companies, the calculus is a blend of regulatory compliance, financial viability, and brand trust.

In the end, the decision to upgrade was not just about a newer phone but about maintaining a lifeline. The story reminds us that in the age of connected health, the line between consumer electronics and medical devices is increasingly blurred, demanding a more robust approach to software longevity.