A fibre tracker built around Caribbean eating.

Overview

Fibre and plant diversity, made practical every day.

Mainstream nutrition trackers tend to emphasize calories, protein, and fat. The Gut Nerd App was designed around fibre and plant diversity, with foods, portions, and eating patterns that are more useful to a Caribbean audience. The product supports both member and administrator workflows in one responsive application.

Challenge

Challenge

Food logging needed to be quick enough for daily use while producing accurate fibre totals from different servings and compatible units. The product also needed to turn raw numbers into understandable progress without overwhelming users, and give administrators practical catalogue and content tools.

My role

My role

I led product discovery, user journeys, wireframes, interface and design-system work, responsive React development, Firebase data architecture, authentication, analytics, and administrator workflows.

Solution

Solution

I built a fibre-first application with catalogue and custom food logging, explicit serving conversions, daily fibre and weekly plant-diversity indicators, editable history, motivational guidance, recipe discovery, and role-aware administration.

Engineering

Engineering

The responsive React application uses Firebase for data, authentication, analytics, and administrator workflows. Firestore transactions keep intake records and summary data aligned, while catalogue versioning supports efficient caching and refreshes. Public recipe content and private tracking data remain separate.

Outcome

What changed.

The completed product brings member tracking, fibre calculations, habit visualization, catalogue operations, recipes, and administrator workflows into one responsive Caribbean-focused experience.

Key points

What the work included.

• Catalogue and custom food logging with clear serving conversions.
• Daily fibre and weekly plant-diversity indicators.
• Editable history, progress dashboard, motivational guidance, and recipes.
• Transactional Firestore summaries for consistent analytics.
• Catalogue caching controlled by a version marker.
• Separate boundaries for public recipe content and private tracking data.
• Role-aware administrator workflows.