Exception-Based Logging: Track Everything in Under a Second

The graveyard of health apps is full of products that asked too much of their users. Supplement trackers are no exception. Most follow the same pattern: open the app, find each supplement, tap to log it, repeat twelve times. Every single morning.

It works for a week. Maybe two. Then life gets busy, and logging becomes the thing you meant to do but didn't. By month two, your data has more gaps than entries.

The problem was never motivation. It was friction.

Why traditional logging fails

Logging each supplement individually treats every day as a blank slate. But your supplement routine isn't a blank slate — it's a habit. You take roughly the same things at roughly the same times. The interesting data isn't what you did take. It's what you didn't.

Think about it: if you take the same 8 supplements every morning, manually confirming each one is pure overhead. The information content of those 8 taps is zero. The only signal worth capturing is the exception — the morning you skipped fish oil because you ran out, or dropped ashwagandha to test whether it was affecting your sleep.

Traditional trackers optimise for completeness. They should optimise for signal.

The exception-based model

Stack Almanac takes a different approach. Once you've set up your protocol — your supplements, doses, and time blocks — the app assumes you took everything on schedule. Your only job is to mark the exceptions.

Skipped something? Tap it. Took an extra dose? Note it. Otherwise, do nothing. Your log stays accurate with near-zero daily effort.

This sounds like a small design choice, but it changes the sustainability of tracking entirely. Instead of a daily chore that takes 2-3 minutes, you have a 1-second check-in on days something changed — and nothing at all on days it didn't.

Better data through less effort

The counterintuitive result: exception-based logging produces more complete data than manual logging. When the default is "everything taken," your records don't develop gaps during busy weeks. The baseline stays intact, and deviations are captured precisely because they're the only thing you need to think about.

This matters when you're looking for correlations later. A dataset with sporadic entries and unknown gaps is nearly useless for pattern detection. A dataset where the baseline is assumed and exceptions are marked gives you clean, continuous data — the kind that actually surfaces insights.

The right amount of effort

Not every supplement decision needs to be deliberate. Most days, your protocol runs on autopilot, and that's fine. The moments that matter are the changes — the days you experimented, forgot, or ran out.

Exception-based logging captures exactly those moments, and nothing more.

[See how it works at Stack Almanac.](https://stackalmanac.com)