About

Hey, I’m Ryan.

Online I’m Noot. I’ve had Type 1 since I was six, and I’m the one person building Ahead. I got tired of waiting for someone else to fix the gaps, so I built the fix myself.

Living withType 1 for 21+ years
Daily setupDexcom G7 + Omnipod 5
Team1 developer, 0 investors
StyleSelf-taught, learns by building

Diagnosed at six

I’ve been doing math about my own body since first grade: carbs, corrections, trends, guesses. Roughly 180 decisions a day that nobody sees. After 21+ years I know this disease like a roommate who never leaves.

I also know where the tools fall short: alarms that go off once you’re already low, data locked inside one company’s app, and gaps between what your devices know and what you get told. Ahead is me refusing to keep living those gaps.

Learning the hard way, on purpose

School didn’t fit me, so I studied on my own and got my GED at 15. Around then I built and ran a game server and its community website from scratch, figured out from console errors and old forum posts.

I build PCs, learned carpentry under an old master carpenter, redid my own porch and roofline, and have made concrete statues for about ten years. Different tools, same pattern: spot the gap, learn what it takes, build it, and let it stand or fall on whether it works.

Why Ahead exists

Most alarms tell you what already happened. Ahead looks at how fast your glucose is moving and whether that’s speeding up or easing off, then tells you early, in one plain sentence. Fast and dangerous gets loud. Slow and harmless stays quiet.

I built it for the tired, burned-out diabetic who needs support most, not the person who already watches every number. I also live with kidney disease, which changes how insulin behaves. Almost nobody builds for that overlap, and it makes me an unusually harsh test case. Every alert you’ll hear went off on my phone first, often at 3 a.m.

How it’s built, honestly

  • One person, a tiny budget, and no app-building background before this.
  • AI wrote a lot of the code. I decide what gets built, test it on a real diabetic body (mine), and answer for every line that ships, whoever typed it.
  • Hundreds of automated tests, with the most around the alert math that matters most.
  • I run the whole stack myself, from this website to the server, so nobody can change a price or a policy out from under you.
  • The Bluetooth connection to the G7 is its own open-source project (GPLv3), kept cleanly separate.

So far

The short timeline

  1. Age 6

    Diagnosed with Type 1

  2. Age 15

    GED, then a first real build: a game server and community from scratch

  3. Summer 2026

    First working Ahead alerts, backend and voice

  4. Fall 2026

    Direct G7 Bluetooth, the portal, family sharing with Ahead Lite, the Pixel Watch app and this website, in beta

  5. Next

    A closed beta with real testers, alerts that understand corrections and exercise, alert intensity you choose, more CGMs, and someday iPhone

Every update, as it ships: What’s new.

Fair questions

What people ask me

Did you really build this yourself, or did AI?

AI wrote a lot of the code, and I’m not hiding that. The decisions, the testing on my own body and the checking are mine. I understand and own what ships.

Why trust a self-taught solo developer with something this important?

Don’t trust me blindly; trust the design. Alerts work without my server, it never gives dosing advice, it runs next to your CGM’s own alarms, and the limits are written down. And it’s tested on a hard-mode body first.

Is Ahead a medical device?

No. It’s a beta companion app, not cleared by any regulator, and it doesn’t diagnose or tell you how to treat anything. Your Dexcom and pump alarms stay your main protection.

How is this different from xDrip+, Loop, Nightscout or the Dexcom app?

Those are great tools. Ahead’s focus is early, trend-aware alerts that stay quiet when things are manageable, a direct G7 connection with no bridge app, family sharing that’s simple for grandparents, and an eye on Type 1 with kidney disease. If another tool works for you, keep using it.

Can I help, test, or just say hi?

Yes to all three. Testers, clinicians, developers, and other diabetics who want to tell me what I got wrong are all welcome. I read what people send, especially the harsh stuff.