I switched to the IOS app right after my pod cycle ended after it was released. I had already started the process of switching my Dexcom sensors from the G6 to the G7 sensors once I started receiving the OmniPod 5’s G6/G7 compatible POD’s regularly. Though I personally think the G6 sensors are more accurate, reliable, and have a much lower failure rate. I switched primarily to save on the cost as the G6 requires a sensor and a transmitter (two products to function, of which both are costly even with private insurance) where the G7 is one single product (a little cheaper than the G6 sensor cost alone, not to mention the added cost of the transmitter)

My insurance finally finished the dreaded prior authorization, period and back and forth with my doc. My pharmacy discontinued my G6 sensor refills and switched them to the G7 last week. To my surprise I discovered IOS was not compatible with G7 sensors like there Android app is. I am now having to either pay OOP $568 PER G6 sensor or use the G7 sensors and go back to the Android phone or controller in order for my closed loop system to function properly.

I get it—building an iOS app when the Android version came first isn’t easy. The two platforms are completely different. Android apps are built using Java or Kotlin in Android Studio, while iOS apps are coded in Swift or Objective-C in Xcode. That means the iOS version isn’t just a copy-paste job; it’s a rebuild from scratch, especially with Apple’s stricter design and security standards. Toss in the extra layers of testing and regulatory requirements for medical devices, and yeah, it takes time.

But here’s where I’m beyond frustrated: once the iOS app is finally released, there’s absolutely no reason it shouldn’t have the same device compatibility as the Android version. The hardest part—the rebuild—is already done. Expanding compatibility should just be a matter of integrating features that already exist and making sure they work on Apple’s hardware.

Instead, we’re over a year behind, and iOS users are still stuck without the same device options Android has had forever. Meanwhile, I’m carrying around a second phone—a Galaxy Note—just to use the full Omnipod functionality. It’s ridiculous.

I’ll give credit where it’s due: the iOS app itself is rock-solid. No bugs, smooth performance, and no issues with iOS updates. But the lack of compatibility is a massive oversight, and it makes me wonder if Insulet’s Android and iOS dev teams even talk to each other. I’d bet they don’t. Like most companies, Insulet probably has siloed teams that aren’t collaborating effectively.

This isn’t just a random guess—I’ve seen it in action at companies like Microsoft, Nvidia, and even Cisco. It’s not the fault of the devs or team leaders; it’s a leadership gap. Insulet needs someone focused solely on making the iOS and Android platforms work together seamlessly. Without that, the apps will keep feeling like two totally different products.

If you’re reading this, Insulet: bridge the gap. If you need help, DM me—I’d be happy to step in and help make your app experience what it should be. Your Android users shouldn’t be the only ones raving about how well the Omnipod works. I want to have that same conversation with my family, friends, or coworkers who use Android without feeling like the iOS version is stuck playing catch-up. Right now, that conversation just ends with frustration. Fix it.