Make daily actions small
The family experience leads with the meal that is due and a direct logging action. Water has a simple add-a-glass control, and member switching keeps individual plans within reach.
Family health & nutrition
Project overviewDDF: Keep the family care journey connected.
DDFProduct videos
DDF — Doctor, Diet, Family — connects Pakistani families with nutrition doctors for personalised meal plans and ongoing support. Family profiles, meal and water tracking, messaging and video follow-ups help households turn dietary advice into a daily routine while doctors review progress.
The family health & nutrition challenge
Different family members have different needs. The daily record and the professional follow-up need enough context to remain connected.
Who DDF connects
Family member
View the relevant plan and daily record.
Family account
Move between the appropriate member views.
Nutrition professional
Review context and guide the next step.
What DDF brings together
Individual context
Keep each member’s plan and record distinct.
Daily record
Present meals, water and routine follow-through.
Professional connection
Link the record to the follow-up conversation.
Follow the journey
01
Set the context
Choose the family member.
02
View the plan
Read the relevant guidance.
03
Record the day
Keep everyday information together.
04
Review
Bring the record into professional follow-up.
Nutrition and care decisions belong with the appropriate professional.
Family record
Member AAdult
Today3 meals · water recorded
MealsMeal entries
RoutineRecorded
Explore the workflow
Doctor · Diet · Family brings individual plans, everyday records and professional follow-up into a connected product story.
Inside the build
The decisions behind the experience.
DDF — Doctor, Diet, Family — is built around households in Pakistan. Family members can have different routines, food preferences and care needs, while a doctor needs to understand what happened between consultations. The product therefore centres on an everyday loop: a personal plan, a simple log and a useful signal for follow-up.
The design brief
Give the doctor a useful account of daily life, rather than a single ambiguous completion score.
A personalised plan only becomes useful when it fits into the ordinary rhythm of a family’s day.
The constraint
An unlogged meal is not the same as a skipped meal. Family-level summaries and individual records must use the same definitions or the doctor sees conflicting signals.
The tradeoff
Separating adherence from logging adds a second measure, but makes missing information visible. The current summary uses planned items as the denominator rather than counting only the logs that happened to be submitted.
Product scope
2
Companion app roles
Family and doctor
3
Care plan options
Solo Care, Family Care and Family Care Duo
2
Adherence signals
Eaten as planned and logged either way
Separate adherence from logging
Not eating a planned meal and not recording anything are different situations. DDF exposes “Eaten as planned” and “Ticked either way” so the doctor can distinguish the plan’s suitability from the logging habit.
Leave room for ordinary life
Meal-swap requests, off-plan foods and reasons for skipped meals provide context. Doctor-created plans can use familiar local dishes rather than treating family routines as exceptions.
A workflow in practice
From the trigger to the handoff.
A representative scenario through the implemented workflow.
- 01 · The situation
A family member skips a planned meal and records the reason.
- 02 · The product response
The daily record distinguishes that logged action from following the plan, while member and family summaries use the same adherence calculation.
- 03 · The next step
The doctor can tell a plan-following issue from a missing-log issue and use that context in follow-up.
How it is built
The structure behind the workflow.
Family & doctor experiences
The current web platform uses React and Vite. Flutter apps provide companion experiences for families and doctors.
Care services
Django manages accounts, member records, diet plans, messages, reports and subscription workflows.
Operational support
Doctor verification and manual payment confirmation are explicit admin workflows. Local reminders and queued mobile records support the daily routine.
Actual product screens
The product, up close.
The family portal gives daily plans and immediate actions a clear place in the interface.
Original product interface captures. Screens use demonstration data; visible figures are not measured customer results.
System map
Connected by design.
SYSTEM BLUEPRINT / DDF
Select a component to exploreConnected by design.
01 The experiences
02 The shared foundation
03 What it connects
THE COMPLETE PICTURE
Individual plans within family care
A shared Django API supports the React web platform and the Flutter family and doctor apps. Admin tools support verification and payment review.
| The work | Problem addressed | With DDF |
|---|---|---|
| Family coordination | Individual plans scattered across conversations | Member-specific plans within a family account |
| Daily follow-up | A chart with little information about actual use | Meal and water logging with context |
| Doctor visibility | A single ambiguous completion figure | Separate adherence and logging signals |
| Plan adjustment | Changes deferred to the next consultation | Messages, reports and plan-swap requests |
Delivered capability
Inside DDF.
DDF brings the family’s daily actions and the doctor’s follow-up into one care product. The result is a practical information loop: what was planned, what was recorded and what the doctor should consider next.
A meaningful health dashboard begins with clear definitions. Recording a skipped meal can be useful engagement even when it is not adherence to the plan.
Evidence & evaluation
What this case study establishes.
Shared adherence calculations and family-summary formatting, supported by the product brief and recorded product screens.
This is a product engineering case study based on source code, project documentation and recorded screens. It describes implemented capabilities; customer performance gains have not been measured for this case study.
What to measure next
Suggested measures for a deployment evaluation, not reported results.
- Logging rate against planned meal items
- Adherence rate against planned meal items
- Agreement between family summaries and member detail
Discuss the fit
Discuss the family and professional workflow, the intended care arrangements and the local operating requirements.