This website uses cookies

Read our Privacy policy and Terms of use for more information.

One of the biggest diabetes tech stories coming out of the 2026 American Diabetes Association (ADA) Scientific Sessions wasn’t announced by a pump company or a CGM maker. It came from the open source community. Developers have made major progress getting Omnipod 5 and Tandem Mobi to work with open source automated insulin delivery (AID) apps like Loop, Trio, and AndroidAPS—a milestone that could open the door to more pump choice for people who rely on DIY systems. 

For the diabetes community, this is a very “We Are Not Waiting” moment. Open source AID was built around the idea that people with diabetes should not have to wait years for companies to deliver the features, flexibility, or device combinations they need. I’ve personally used open source Loop for years, and I’ve also tried Trio, so this is not just a technical story to me. It is about access, choice, and the ability for people with diabetes to use the algorithm that work best for their lives with the device of their choosing. 

I spoke with James Woglom, an open source developer who has worked on several diabetes tech projects, including Tandem and Nightscout integrations. Woglom emphasized that this is not the work of one person, but the result of years of community development. “We build on top of giants,” he said, noting that the work to understand earlier Omnipod systems like Eros and Dash helped make this latest progress with Omnipod 5 possible. 

The biggest near-term development is Omnipod 5. According to Woglom, the open source community has been trying to connect Omnipod 5 with Trio, Loop, and AndroidAPS basically since the system launched. That work has taken years, with developers hitting—and slowly working through—one roadblock after another. Earlier this year, Woglom said the team was able to break through a final major barrier, allowing the pieces to come together quickly. Omnipod 5 support is now in a small closed beta group for Loop and Trio users, with roughly 10 testers submitting logs and helping developers track down bugs before a wider release. 

If the current timeline holds, Omnipod 5 support for Loop and Trio could move into an open beta by the end of the summer, with broader availability expected by the end of the year. For users, the experience would be more like using Omnipod Dash with open source AID, where the phone communicates with the pod and the CGM communicates with the phone. That also means the different Omnipod 5 pod versions tied to Dexcom or Libre compatibility may matter less in the open source setup, because the pod would not be directly communicating with the CGM the way it does in the official Omnipod 5 algorithm. 

Tandem Mobi is a different story—and potentially an even bigger milestone. If open source support becomes usable, it would mark the first time an open source AID system supports a Tandem pump. Woglom said the community is already able to communicate with Mobi, but there is one major practical barrier: the pump beeps or vibrates whenever a bolus command is sent from the phone. In an open source AID setup, where the algorithm may be issuing commands every five to ten minutes, that could mean the pump is constantly vibrating or making noise. Until Tandem offers more silence or snooze controls, that limitation could make Mobi technically possible but difficult to live with in real-world use. Perhaps the diabetes community can urge Tandem to introduce more customizable alert settings for its own users, that the open source community could ultimately take advantage of… 

Interestingly, Woglom’s Tandem work also predates this latest Mobi effort. He created tools that allow Tandem users to push pump data to Nightscout and also built an open source Android app that allowed some Tandem users to interact with Mobi before Tandem released its own Android support. His app even includes Android Wear support, allowing users to bolus from a watch through the phone. Looking ahead, Woglom said the goal is to have Mobi working with Trio, Loop, and AndroidAPS by the end of the year, though real-world feasibility may depend on whether Tandem addresses the vibration and beeping issue. Omnipod 5 support for AndroidAPS is also in development, but appears to be earlier-stage, with broader usability more likely in late 2026 or early 2027. 

For people in the open source community, the headline is clear: the next generation of popular pumps may not be locked out of DIY systems forever. There are still important caveats—this is not FDA-cleared, not manufacturer-supported, and not ready for most users today—but the progress is meaningful. For years, open source users have had to make decisions based on which pumps could be looped, not necessarily which pumps they most wanted to wear. If Omnipod 5 and Tandem Mobi become viable options, that could give people with diabetes more freedom to choose the form factor, algorithm, and ecosystem that works for them. And it could eventually mean a second tubeless option for DIY-ers as tubeless Mobi is headed to the FDA later this year.

What do you think of the news? Let us know in the comments and follow our free newsletter for more.

Want more?

For the latest diabetes tech, join our free newsletter.

If you like our content and want more, join Diabetech All Access—unlocking exclusive Live Q&As, giveaways, stories and industry analysis. Your support helps sustain our independent journalism and keeps this platform thriving.

Disclaimer: Diabetech content is not medical advice—it’s for educational purposes only. Always consult with a healthcare team before making changes to your treatment.

Reply

Avatar

or to participate


Keep Reading