IMIN is a wellness app that reads biometric data — heart rate, breathing, recovery — and turns it into something a regular person can actually use. The early version worked. The problem was that almost nobody wanted to open it twice.
The starting point: accurate, but cold
The original results screen was, functionally, correct. Numbers, labels, a chart. But it read like a lab report, not something built for a person checking in on their own body. Accuracy alone wasn't earning a second visit.
Finding the actual question people were asking
Nobody opens a wellness app wondering "what is my exact resting heart rate variability." They're asking something simpler: "how am I doing today, and is that normal for me?" Once that became the design brief, the whole hierarchy of the screen changed — plain-language summary first, supporting numbers second, raw data available but no longer the headline.
The data didn't change. What changed was which question the screen was actually trying to answer.
Designing for a glance, not a study session
Most people check an app like this for a few seconds, not a few minutes. That meant one clear takeaway per screen, color used to communicate at a glance (a strong green for "resilient," a soft one for "steady"), and detail tucked behind a "go deeper" tap for the smaller number of people who want it.
Consistency across the whole flow
The results screen, the dashboard, and the education library all needed to feel like one product, not three separate builds stitched together. A shared type scale, consistent card treatment, and one color language throughout made the app feel considered instead of assembled.
The result
The same underlying data, presented as something closer to a daily check-in than a report — which was the entire point all along. Good design, in this case, wasn't decoration on top of the data. It was the thing that made the data usable at all.