Nittoo
Turns everyday purchases into container lifespans, true daily costs and calibrated run-out windows.
TL;DR
A personal consumables tracker and forecasting app that turns everyday purchases into container lifespans, true daily costs, and calibrated run-out windows. Source: README.md:5 @ b0fb0fb.
Context & motivation
Modelling pack sizes only per product distorted lifespans when people bought different bottle sizes. Nittoo forecasts run-out from size-normalised consumption rates learned from each user’s completed cycles, shows a calibrated P10–P90 window once enough history exists, and shows “First cycle • Learning” instead of a guessed number for first-time items. Source: README.md:104–107, 178 @ b0fb0fb.
My contribution
- Built the React + Supabase app: container-level tracking, run-out forecasting and restock reminders, with Row-Level Security tenant isolation verified in CI.
- Built the Forecast Lab: a Pydantic + JSON Schema export contract, a seeded household simulator, idempotent DuckDB ingestion with a rejects quarantine table, and a dbt warehouse.
- Backtested forecasts with rolling-origin evaluation and exported calibrated interval quantiles and parity fixtures back into the app.
How I used AI tools
Implementation by an AI coding agent (Google Antigravity). I set the scope, approved every plan, ran the checks, and accepted only work that passed automated gates.
Key decisions
Ship rate_mean (rule_only)
- Alternatives
- rate_mean (rule_plus_rate_outlier), the mechanical winner
- Why
- The extra gain was small, degraded under noise and elasticity, and shipping the simpler model avoided porting an unreliable detector.
- Trade-off
- Gives up that small extra gain (95% CI documented in the backtest report).
Per-purchase pack-size overrides with rate normalisation
- Alternatives
- Pack sizes modelled only on products
- Why
- Modelling pack sizes only on products distorted lifespans when users bought different bottle sizes.
- Trade-off
- Rate normalisation assumes consumption pace does not scale with container size; if larger bottles are used noticeably faster, lifespan can be overestimated.
Move data-quality checks (zero-day, outlier, referential) into dbt intermediate models with singular and warning SQL tests
- Why
- Keeps raw ingestion fast while surfacing auditable quality metrics.
Challenges
Results
Limitations & next steps
- Real opt-in usage data is needed to measure actual pack-size elasticity. source: README.md:187 @ b0fb0fb
- Currency formatting defaults to BDT; per-user currency preferences are planned. source: README.md:188 @ b0fb0fb
- Restock reminders surface in-app only (Dashboard and Product Detail); background Web Push alerts are planned. source: README.md:189 @ b0fb0fb
Data sources
- Data: Synthetic (metrics)README.md:87 @ b0fb0fb
- Metric: Overall holdout forecast error (MAE), size-normalised rate forecast shipped in the app vs the app’s original average-duration baseline, synthetic data (4.53 days)README.md:89–93 @ b0fb0fb · rate_mean (rule_only) vs baseline (none) · 2026-11
- Metric: Forecast error (MAE) after pack-size changes, size-normalised rate forecast shipped in the app vs the app’s original average-duration baseline, synthetic data (4.88 days)README.md:89–93 @ b0fb0fb · rate_mean (rule_only) vs baseline (none) · 2026-11
- Metric: P10–P90 run-out window coverage on holdout, size-normalised rate forecast shipped in the app, synthetic data (83.7%)README.md:95 @ b0fb0fb · rate_mean (rule_only) · 2026-11