CASE 03 / 04DADBOD   /   FIELD NOTESCLOSE [ESC] ×
// 01   SUMMARY READOUT

DADBOD

A calorie and diet-planning app with TDEE and carb-cycling logic.

ROLEFrontend Engineer
DATES / ENGAGEMENTFREELANCE · 2022
STACKReact · Redux · Responsive UI
// 02  THE PROBLEM

A diet-planning application needed to turn calorie calculations into a clear daily plan on a tight deadline. Users needed a responsive experience for TDEE calculations and carb- or keto-cycling plans.

// 03  WHAT I BUILT
01 / TECHNICAL DECISION

Make the calculation flow explicit

Built TDEE calculation and carb/keto-cycling logic into the planning experience. Users move from their inputs to a calorie and diet plan.

user inputs → TDEE → calorie target → diet plan
02 / TECHNICAL DECISION

Keep state predictable

Built the interface with React and Redux, keeping the plan and the user's inputs coordinated across the application.

inputs → Redux state → calculations → views
03 / TECHNICAL DECISION

Ship for small screens

Delivered a fully responsive application within a tight deadline. The product reached about 1,000 monthly users internationally within its first year.

mobile ↔ tablet ↔ desktop
// 04  RESULTS / KNOWN NUMBERS
~1,000MONTHLY USERS
01FIRST YEAR
GLOBALINTERNATIONAL REACH
// 05  SYSTEM ARCHITECTURE
FIG. 03 — SYSTEM MAPARCHITECTURE / NOT A PRODUCT SCREEN
01USER INPUTS
02TDEE
03CALORIE TARGET
04CYCLING PLAN
Interfaces are only one part of the system.
// 06  WHAT I’D DO NEXT

I would separate the calculation rules into a well-tested domain module and improve the explanation of how each target is derived. Clear assumptions matter in a planning tool: the user should be able to understand the result and adjust their inputs.

DISCUSS A PROJECT ↗