PRODUCT ENGINEERING CASE STUDY

A GLP-1 companion built around context—not another weight chart.

THE PRODUCT QUESTION

How do you make a medication journey easier to remember, understand, and discuss?

Weight alone leaves out medication timing, appetite, nausea, fatigue, constipation, nutrition, hydration, activity, sleep, and glucose. BodyReply organizes those signals into a daily companion and a care-visit recap—without crossing into diagnosis or dosing.

INTERACTIVE BUILD

Explore the product with synthetic data.

The public demo exposes the complete journey UI without requiring an account or presenting fabricated information as a real patient record.

Launch the demo ↗
SYSTEM DESIGN

One normalized timeline across the product.

InputsDaily check-insMedication contextDexcom / Oura / WHOOPApple Health / Health Connect
→
BodyReply layerIdentity + consentEncrypted connection tokensNormalized health samplesDaily summaries + evidence
→
OutputsToday’s replyJourney patternsHabit supportCare-visit recap
Next.js + VinextCloudflare WorkersCloudflare D1Drizzle ORMHealthKitHealth ConnectOAuth 2.0TypeScript
KEY PRODUCT DECISIONS

Make the useful boundary visible.

Track the prescribed plan; never invent one.

Dose fields reflect what a user enters. BodyReply does not recommend escalation, skipping, substitution, or timing changes.

Explain what evidence supports a reply.

Every summary shows whether it came from entered goals, recent check-ins, connected signals, or illustrative demo data.

Use a public demo instead of fake production claims.

Portfolio visitors can explore a complete experience built with synthetic records while authenticated accounts remain private.

Design provider gates honestly.

Dexcom, Oura, WHOOP, Garmin, and Abbott states distinguish working adapters from credentials, approval, or commercial partnership requirements.

WHAT IS IMPLEMENTED
  • D1-backed accounts, plans, daily check-ins, waitlist, and normalized health records
  • Encrypted OAuth token storage and adapters for Dexcom, Oura, and WHOOP
  • Native iOS HealthKit and Android Health Connect companion projects
  • Interactive journey dashboard, symptom logging, progress visualization, and care recap
  • Responsive public product story, demo, privacy, terms, SEO, and accessible states
WHAT REMAINS EXTERNAL
  • Production provider credentials and commercial approvals
  • Apple and Google developer enrollment and store review
  • Formal clinical, privacy, security, and regulatory review before consumer release
  • Prospective validation with real users and qualified health professionals
  • A trained prediction model; current pattern replies are descriptive and rules-based