She has had Type 1 diabetes since she was young. I have spent years watching her navigate fingersticks, site changes, sensor warmups, and the exhausting mental load of T1D — the constant background calculation that never fully turns off. I wanted to at least make it lighter. Not just for her, but for everyone in her circle who worries when the number goes quiet.
I showed her the idea early on — just a concept, nothing built yet. She asked when she could use it. My first honest thought was that this might be impossible. I had never built a mobile app. I had never published anything to the App Store, set up a developer account, integrated a medical device API, stood up a backend database, or packaged an app bundle. I did not know where to start.
So I started anyway. One experiment after another, self-teaching every piece — React Native, Expo, Node.js, MongoDB, OAuth 2.0, the Dexcom API, App Store Connect, TestFlight. Each thing I did not know how to do, I figured out. That process is how LinkLoop got built.
The gap I kept running into was the circle problem. Her Dexcom app showed her numbers. Dexcom Follow let me see them. But there was no single place where everyone who mattered — family members, the people who check in at 2am — could see the same thing, get the same alerts, and stay in the same loop without requiring each person to create a Dexcom account or be technically savvy enough to set up Follow.
LinkLoop is the answer to that problem. One app, two roles. The Warrior connects their Dexcom and controls who sees their data. Their Care Circle joins with a private invite code and sees the same live readings — no Dexcom account required, no complicated setup. Everyone is in the loop, or no one is. The warrior decides.
The answer to her question is: soon. Spring 2026 for the App Store. TestFlight beta now. She gets to try the app her question helped complete.