Health & wellness · 2025 · iOS + Android
AnfCare
A wellness product around wear-window packs — recovery, strain, and sleep, with a protocol people can actually finish.
Technical Product Owner + Mobile Engineer
Wearables
Timed health packs
Sleep
Recovery and strain
iOS + Android
Both stores
Click any screen to zoom
01
Context
AnfCare is a health product built around daily rhythm: recovery, strain, sleep, and wearable “packs” — sensor sessions with a wear window, not a generic step counter. The brand line is restore your daily rhythm. The app has to hold clinical-feeling metrics (HRV, RHR, SpO2, temperature, sleep stages) without looking like a hospital portal.
02
My role
I owned
- Product framing: rhythm and packs, not a feature dump
- Home, packs, learn, and profile IA
- Wear-window UX and session states
- Flutter implementation and data presentation
- Cognitive training as a secondary loop in profile
The team owned
- Sensor hardware and firmware
- Health data pipeline and scoring models
- Clinical / brand art direction
03
The problem
Wearable health products often fail in the same way: they show too many numbers, or they hide the protocol the user must actually follow. AnfCare’s user is wearing discs for a timed window. If the app panics them, they take the sensors off. If it under-explains, the data is junk.
04
Discovery
The core loop is not “open app, see dashboard.” It is: understand the pack, place sensors, leave them on, come back to recovery and sleep. Home is the scoreboard. Packs is the protocol. Learn is education. You is identity, health, and mind games. We designed for a wear window that continues when the screen is closed.
05
Product decisions
Packs are a protocol, not a setting
- The decision
- A pack session is a guided flow: what you track (e.g. coherence), where the discs go, how long the window is, then a live timer that survives leaving the screen.
- Why
- The hardware only works if the human completes the window. The app’s job is adherence, not decoration.
- The trade-off
- Fewer playful shortcuts. More instructional UI than a typical fitness home.
- The result
- Users get a wear window (hours remaining), placement diagram, and a clear rule: you can close this screen — the timer keeps running.
Home shows recovery, strain, sleep — not everything
- The decision
- Lead with a recovery gauge and four vitals, a strain score out of 21, and sleep staged as a bar. Workouts are present but allowed to be empty.
- Why
- Rhythm is the product. A wall of charts would compete with the pack loop.
- The trade-off
- Power users may want deeper labs immediately. Those sit behind Health in profile.
- The result
- The first screen answers “how am I today?” in one scroll.
Mind games stay in You, not Home
- The decision
- Cognitive training (reflexes, memory, focus) lives in the profile area with session counts — not as a competing tab.
- Why
- Home is physiological. Mixing brain games into recovery would blur the product.
- The trade-off
- Discovery of mind games is weaker. Brand focus is stronger.
- The result
- The tab bar stays Home, Packs, Learn, You. Mental fitness is optional, tracked, and quiet.
06
UX / user flow
Warm cream, plum, and gold. Sign-in is unhurried. Home is carded metrics with a gold active tab. Pack flows use serif headlines, line-art sensor maps, and a gold primary button (Begin pack). Profile overlays a lifestyle still with initials, then Overview / Health / Mind games. The whole product is supposed to feel like a studio, not a tracker.
07
Technical architecture
Flutter client with a session-oriented domain: packs, wear windows, and daily aggregates (recovery, strain, sleep stages). Auth includes email and Google. Sensor placement and timers are client-driven; scores come from the health backend. Empty workout states are first-class so the UI never looks broken on a rest day.
08
What I built
- Sign-in and join flow
- Recovery, strain, and sleep dashboard
- Pack catalogue and wear-window session
- Sensor placement guidance and running timer
- Profile, health, and cognitive training
- iOS and Android client
09
Trade-offs
We did not turn Home into a research console. Historical compare, raw sensor dumps, and social sharing waited. The first product had to make wearing the pack feel obvious and make this morning’s rhythm readable in under a minute.
10
Launch
Shipped as a branded wellness client for iOS and Android, with packs as the hardware handshake and Home as the daily read.
11
Outcome
The product presents recovery, strain, sleep, and pack adherence as one rhythm story. Hardware and scoring remain with the clinical/technical partners; the mobile layer is how people actually complete the loop. Specific clinical claims stay with the product owner.
12
What I learned
In wellness, tone is a product decision. If the UI shouts, people treat sensors like a gadget. If it is too quiet, they miss the protocol. I would prototype the wear-window empty states with real time-to-complete data before locking the pack copy.