T1D Logbook

Fast logging: tap a chip, type your dose, then just hit Send three times — extended, prebolus, and BG all default to the sane answer on a blank Send.

Dosed late? Enter prebolus as a negative number, like "-30" — it shows as "30 min LATE" instead of forcing you to lie and say 0.

Didn't finish a meal? History → 🍽 Adjust eaten. Fraction (1/2), decimal (.5), or type the actual grams. Your dose stays what you really gave.

Eating more than one thing? Tap 🔗 Add to plate — pick from what you've had there before, or type something new and it saves itself for next time.

Building a repeat order? Tap 🔗 Make a meal on the Log tab, pick the foods, and either log it once or save the combo for good.

Tired of scrolling to the same few meals? Tap ⭐ on them — favorites jump to the top of your quick-tap chips and your library.

Want a food's whole history? Tap its 📊 name — in your library, or on a past entry — and see every time you've logged it, pattern already worked out.

Considering Nightscout? Genuinely worth it, but setup is real work — doing it entirely on a phone can easily run several hours. A computer makes it meaningfully easier, and Claude Code specifically makes it fast. Paid, done-for-you hosting (like Nightscout Pro) skips the DIY setup entirely, for a price.

Want a number to count as Searched instead of a Guess? Tap 🔍 Look it up before typing the carbs — do that and it labels itself automatically.

Worried a meal's been running rough? Check the tap-to-dose screen before you commit — the heads-up shows up right there, not just buried in History.

Already know a food is solid without waiting on a streak? Set it to Trusted yourself in Meals tab any time — you don't have to wait for the app to ask.

Want to skip the "still Guess/Searched" nudge for something you already trust? Mark it Trusted and it stops flagging that entry — the nudge only checks foods still sitting as Guess or Searched.

Want a BG that goes out of range to count as trouble even when you didn't log a correction for it? Set your goal range in Options → Also count a BG below/above as trouble.

Eating something slow to digest — pizza, anything heavy? Widen your Meal watch window in Options so the app keeps reaching for real readings that far out, instead of stopping short.

Reviewed a meal on History's risk list already? Tap the ✕ next to it — it'll go quiet until you log that food again, so it's not nagging you about the same thing twice.

Hunting for one specific food in a long list? Switch Sort by (top of Meals tab) to A-Z instead of scrolling past favorites to find it.

Merging two spellings with different carb counts? Pick whichever number you actually trust more when it asks — or Cancel to back out and leave both untouched if you're not sure.

Never use extended/split bolus? Options → Logging preferences → turn off the question, and it stops asking for good.

Receipt scan botch a name? Just edit it right on the scan — the app remembers your correction for next time.

Same food, different spelling on two receipts? Meals tab → ⇄ button — merge them into one, or teach it the new spelling. Scanning something close to what you've already saved also just asks if it's the same thing.

Back it up every couple of weeks once you've got real history: Options → Export full backup.

About to change a food's carb count? Tap ✎ in Meals — it shows that food's own history (last time, average dose) before it asks for the new number.

Adding something similar to a food you already have? Choosing "None of these — add new" shows that food's history as a reference before you type carbs on the new one.

Want a food's full history without digging through the History tab? Once it has real history, its dose screen links straight to it.

Gen 13.0 — The beginning of the narrator. Before a word of it was built, what it may and may not do was written down: it can explain what your data shows and point at patterns, including when a setting looks out of step with your own curves — and it can never turn a measurement into an instruction, name a dose, or tell you what you should do. That isn't a promise sitting in a document. Every explanation it writes is checked before it reaches your screen, and one that reads as advice is withheld rather than shown with a warning attached. It also has to wear its guesses as guesses: what it knows, what it's guessing, and what it was never told stay visibly different things. It's in testing, off unless you turn it on, and it runs on a key you supply to your own AI provider — nothing goes anywhere until you ask it something. It arrives when it passes.

Gen 12.9–12.11 — The split got a helper: type your total and the app shows you the math of your fraction before you commit to it, per meal, without touching your usual setting. A ⏰ button hands the reminder to your phone's own timer, so it still finds you when the app isn't open. Search arrived in two places — your food library and your own history. Photos learned to protect you: the location and camera details are stripped out of the picture by the way it's saved, not filtered afterwards, and any backup carrying photos now says out loud that the file isn't encrypted. The app also stopped lying about a failed save — if your phone's storage is full, the entry says so instead of showing a tick, and nothing already in your history is touched.

Gen 12.1–12.8 — The pen rework: tell the app how you dose and it pins your last shot to the top, gives you one tap for your long-acting, and tells you what's still working from the last one when it asks your units. Split dosing landed properly, and it wasn't designed at a desk — it was forged over the creator's own dinners. Every slow, fatty meal that ran long changed what the feature had to do next: dose part now, hold the rest, and have the app come back when it's time to decide, with your chart in front of you rather than a number in a vacuum. The held part doesn't pretend to be insulin you've taken, because you haven't taken it yet. Extended and split stayed separate on purpose: one is your pump stretching a dose, the other is you deciding twice, and they're not two versions of the same thing. A Food Library opened behind the log, with restaurant meals whose numbers trace back to the page that published them. Meal photos, a feedback button that comes straight to me, and a first-run setup that offers to help rather than making you find everything yourself.

Gen 12.0 — The first certified build. From here on a version isn't something a build script prints — every artifact is recorded against the fingerprint of its own bytes, checked by a second pair of eyes that didn't build it, and verified again after it goes live. It sounds like bookkeeping. It exists because a build once shipped wearing the wrong version number and nothing on the screen could have told you.

Gen 11.1–11.9 — Nutrition beyond carbs: a profile, daily goals, and progress you can actually see against them, for the days when carbs aren't the only thing you're watching.

Gen 11.0 — Removed the internal development checklist that lived behind the greeting card — that was scaffolding for building this app, not something that belonged in the app itself.

Gen 10.8 — Quick log: type "quick log [name] (carbs) (dose)" and confirm once, instead of stepping through the guided flow. Editing any entry can now flag its carbs as likely under- or over-counted, for the times sauces or sides weren't fully counted the first time.

Gen 10.6–10.7 — Correction check got a real overhaul: choose whether recent corrections should fade gradually or only count within a set window, or see both at once. The math itself now uses each correction's actual lowest point reached, not a snapshot at a fixed time — and it checks its own inputs, skipping (and telling you about) any correction whose follow-up wasn't close enough to trust, or where something else got logged in between. It also now tells you honestly whether your set correction window actually fits your own data. A number at or below zero always comes with a plain warning: never a dosing number, always a pattern to bring to your care team.

Gen 10.3–10.5 — Renamed to T1D Logbook throughout. The Log tab now only shows what you've actually favorited by default, with everything else tucked one tap behind "More actions." A new Reports panel gathers Pod report and Correction check in one place, plus two real exports — a text summary, or the same summary with your actual chart embedded. The Chart tab can now show Exercise and Cycle entries as real markers too, each with its own toggle.

Gen 10.1–10.2 — Exercise, sick/stress/vacation, and cycle tracking, each with their own quick log. Pod changes now ask where you placed it and whether it failed early, feeding a fuller Pod report. Battery tracking, quietly checking whether an installed icon or widget is actually costing you battery life. Every panel in Options can now collapse — and remembers what you leave open.

Gen 10.0 — Nightscout support: connect your own continuous data source, with automatic fallback to Dexcom/Libre if it's ever unreachable. The Chart tab became a real, flowing 24-hour view instead of just per-meal snapshots, with a custom time window and a Share panel for sending a link.

Gen 9.2 — A food's own history now shows right when you're deciding on carbs — editing an existing one, or adding something new that's similar to it. Fixed a real matching bug: foods from the same place were sometimes falsely flagged as similar just for sharing a venue name, even when the dishes were completely different. History's "back to all meals" is no longer a hunt. About app actually describes what's in the app today.

Gen 9.1 — The app can now open with no signal at all. Everything already lived on your phone — now the app itself does too, as a fallback for when you're offline; online always still wins when you have it. Tips got reworked into genuine how-tos throughout, instead of reading like a list of what changed.

Gen 9.0 — The app can now speak up first: after a genuine clean streak it may ask to mark a meal Trusted, and it'll point out when your last log is still Guess or Searched once there's real history to show. Trouble detection now watches the actual numbers too, not just what you logged — and that same window genuinely controls how far the app reaches for real CGM data, nothing hidden or capped behind the scenes. Merging two foods with different carb counts asks which to keep. History's risk list can be cleared once you've seen it, library sorting is yours to pick, and typing something that partly matches other foods now offers a clean way to add it as new.

Gen 8.1 — The app watches your patterns for you: a meal with a rough track record flags itself before you dose, not just after. It notices when things are improving or getting worse, and calls out dosing late specifically when that's the actual reason a meal runs rough. Carbs now sort into Guess, Searched, or Trusted automatically — no more being asked. A big dose swing from last time gets flagged, with a threshold you control.

Gen 8.0 — Add to plate and Make a meal, for building a meal from foods you already have. Receipt scanning learns a new spelling instead of quietly duplicating a meal. Every food shows how many spellings it knows. Favorites, and a real Food Library / Meal Library — everything stays in Food Library permanently, and anything worth quick access can also live in Meal Library. Tap any food's name to see its whole history in one place.

Gen 7.1 — Export CSV moved to Options, alongside full backup. History tab cleaned up.

Gen 7.0 — Mark carbs trusted or a guess, with trusted carbs locked against accidental edits. 🍽 Adjust eaten for correcting what you actually ate without touching your dose. 🔗 Combine meals and ⇄ merge/teach-a-spelling. CGM auto-sync in the background, and a real fix for reconnecting after a dropped connection.

Gen 6.0 — The original build: meal logging with dose history and BG curves, receipt scanning, CGM sync (Dexcom and Libre), and the blank-Send shortcuts that let a normal entry go tap, type, Send, Send, Send.

You're the only person present for every single meal, every dose, every pod change — not your doctor, who sees a twenty-minute snapshot a few times a year, and not an app guessing from a photo. This app's whole job is making sure that firsthand knowledge is not forgotten. It turns your own history into something you can actually see and trust — not a prediction, just what genuinely happened, remembered for you to see when it matters, right before you dose.

Tap a chip, type a meal, or scan the receipt — your meal log lives on your device, and your logs are never sent to anyone else's. Connect your CGM (Dexcom or Libre) and curves attach themselves, or enter BG by hand — no CGM needed.

Every food sorts into Guess, Searched, or Trusted on its own — search first for Searched, type cold for Guess. Only Trusted locks the number, and that's always your call, never the app's.

When a food's numbers come from the nutrition library, every number traces to the real page or label that published it, with a saved copy of that source behind it. A carb count isn't kept because it looks about right. If a source doesn't list a nutrient, you see "unavailable," never a zero. If the same food ever gets entered twice, you can merge them so they share one history. And not all sources are equal: an official page, a manufacturer's label, a database match, and an estimate are each labeled differently, so you always know how solid the ground is under a number while your history builds. An estimate should always look like an estimate, not a published fact.

The app watches your own patterns and speaks up when it's worth knowing: a meal running rough flags itself before you dose, not just after. A genuine clean streak may get a suggestion to mark something Trusted. History leads with what's actually worth a second look, instead of making you go hunting for it.

Everything else — Food and Meal Library, receipts that learn your spellings, merging duplicates, backup and CSV export — exists to make logging fast enough that you'll actually keep doing it.

Your record, your device, your numbers, your call on dosing — you and your pump make the decisions.

Whenever the app shows you a pattern — like how a meal usually affects you or how much a food has moved your blood sugar before — it is using your own history. Here is how it looks at that history and what it will not do.

Better records count more. Not every logged meal gives the app the same amount of useful information. A meal with complete glucose data tells the app more than one where the sensor dropped out for half of it. The app does not count every meal as equal just because it exists. A complete record counts more. A record with missing information counts less. That means three solid meal records may be more useful than five incomplete ones, and the app treats them that way.

Missing stays missing. When glucose readings are missing, the app does not draw a line through the gap and pretend those readings happened. When you mark a reading as bad — such as a compression low or another sensor problem — it no longer counts toward the pattern. The record of why it was excluded is still kept. The app does not quietly keep bad data, and it does not quietly erase it. A blank is the truth. A made-up number is a lie.

A small amount of history stays small. The app always shows how many times a pattern is based on. Two meals should not suddenly become a confident conclusion. The more good history a food or meal builds, the more useful the pattern becomes. Even then, the app should never act certain. Your body can react differently from one day to another, even when the meal looks the same.

Predictions are only judged on what they did not already know. When the app makes a forecast, that forecast has to be saved before the result happens. Only those ahead-of-time forecasts count when checking whether the prediction system is working. Looking at the result afterward and fitting a neat answer around it does not prove the app predicted anything. That kind of after-the-fact match gets no credit.

This is not a dosing recommendation. The goal is to make your own history easier to understand. It may help you see what happened before, how consistent it was, and how much information the pattern is based on. It does not tell you how much insulin to take. You and your pump still make the dosing decision.

I'm not an app developer. I'm a type 1 diabetic who got tired of guessing how many carbs were in a meal — and of never remembering what I dosed for it last time, or how it went.

I built this with AI. Claude, specifically. About six months ago I tried the same thing with ChatGPT: it wrote plenty of code, but never a working app. It told me I could go learn Python. I didn't, and I scrapped the whole idea. Six months later the tools are good enough that this actually exists — and I use this app every day.

I'm also using this project to figure out what AI actually is and what it can really do. Building something real, that I actually rely on, seemed like the only honest way to find out.

So: this is early, and there will be bugs. The upside of early is that features are cheap to add. If something breaks, or you catch yourself thinking "this would be great if it just…" — tell me. Getting other people's perspective is the entire reason I'm sharing it.

One thing I'd push you on: back it up. Everything you enter lives on this phone and nowhere else — that's the privacy, and it's also the risk. The longer you use it, the more your meal library and history are worth, and the more it would sting to lose them. If anyone ever tells you to "clear your cache" or "clear site data" to fix a browser problem, that wipes it. Options → Export full backup is the real restore file. Do it every couple of weeks once you've got history worth keeping.

The CSV is a different thing: it's your log laid out as a spreadsheet — every meal, dose, prebolus, and the blood sugar curve that followed. If you spot a pattern worth showing your doctor or diabetes educator, that's the file to bring them. It's readable by a human, not just by this app.

Everything you enter stays on your phone. Nobody sees it, including me. This is a logging and pattern tool, not a medical device — it never recommends a dose. You, your pump or pen, and your care team make every call.