WEB / IOS / ANDROID

NutriTrace

Food and symptom tracking with correlation analysis, built for figuring out what’s actually triggering you.

Try it live

ViteTypeScriptCapacitorStripe

AT A GLANCE

Correlation

Engine

Structured

Elimination Protocols

Platforms

Shared

Timeline

THE PROBLEM

Feeling worse after meals shouldn’t require becoming your own data scientist

Figuring out which food is behind a symptom usually means keeping two separate logs and trying to eyeball a pattern across weeks of notes — slow, error-prone, and easy to give up on before an answer emerges.

HOW IT WAS BUILT

One timeline, with the correlation math built in

NutriTrace is a Vite and TypeScript app, shipping to web and native mobile through Capacitor, built around a single shared timeline for food and symptom entries.

Correlation analysis runs against that timeline directly, and structured elimination-protocol support keeps a testing phase and its results attached to the same record instead of scattered across notes.

INSIDE THE PRODUCT

Core surfaces that define the experience

Logging

Food and symptoms, one timeline

Meals and symptoms are logged against the same clock, so the data needed for correlation exists from the first entry rather than being reconstructed later.

No separate spreadsheets to reconcile.

Analysis

Correlations surface on their own

The app runs the statistical work of connecting foods to symptoms, turning a pile of entries into a ranked set of likely triggers.

The pattern-finding is the product, not an afterthought.

Protocols

Elimination phases stay structured

Starting and tracking an elimination protocol is a first-class flow, keeping what was removed and what changed clearly attached to each other.

Built for the actual discipline elimination diets require.

KEY FEATURES

What makes it work

Correlation, Not Just Logging

Food and symptom entries share a timeline, and NutriTrace surfaces the statistical correlations between them, turning raw logs into an actual hypothesis about what’s causing what.

Structured Elimination Protocols

Elimination phases are modeled explicitly in the app rather than tracked in a separate notebook, so a protocol and its results stay attached to the same data.

Nutrition Goals Alongside Symptoms

Personal nutrition goals sit next to symptom history so progress and triggers are visible in the same view, not two disconnected tracking systems.

WORKFLOW

How a trigger gets identified

NutriTrace is built around turning weeks of food and symptom entries into an actual answer, not just a longer log.

Log meals and symptoms as they happen

Both feed the same timeline, so the correlation engine has real, time-stamped data to work with from day one.

Let correlation analysis do the pattern-finding

The app surfaces which foods statistically track with which symptoms instead of leaving the user to eyeball weeks of notes.

Test the leading hypothesis with a structured protocol

A guided elimination phase turns a correlation into a confirmed trigger, with nutrition goals tracked alongside the whole process.