Case study
Affili-Fit
Meal plans, workouts and the grocery run in one app.
- Role
- Senior Software Engineer and Team Lead
- Zee Palm
- When
- Zee Palm era
- Where
- Client delivery
The problem
What made this hard
Fitness apps usually stop at the workout. Affili-Fit follows the whole week: what to eat, what to train, what to buy, and how the family is doing, with the wearable data pulled in rather than typed in.
What shipped
Built, wired, released
The week, planned end to end. Meal plan generation and workout plans, with a training studio for guided sessions.
Grocery lists that sync against a pantry. The shopping list only contains what the kitchen is missing.
Progress that includes other people. Weight and goal tracking with charts, family accounts, a community feed, and a rewards program with partner-created offers.
Wearable data pulled in, not typed in. Apple Health and Google Fit reads for steps, heart rate, active energy and walking distance through the health package.
The retail details. Algolia-backed search, barcode scanning for foods, PDF export, and an in-app wallet.
Architecture
How it holds together
L0Feature modules per domain (meal plan, workout plan, grocery, rewards, family), each with its own controllers and views.
L1Firebase as the backend of record with Cloud Functions for plan generation and rewards, Algolia mirroring searchable content.
L2Health data flows one way, from the platform APIs into tracking cards, which keeps permissions honest.
Screens
From the actual build
Every frame is a real capture unless labeled otherwise. Tap any screen to open it.
Outcome
Where it landed
- Shipped as a production Flutter app at Zee Palm; version 1.7 at last count.
- The screens above are frames from the product's own Figma file, labeled as design frames rather than passed off as device captures.