From a static sleep report to an interactive understanding of sleep health
SleepFit helps people understand what happens while they sleep. The device tracks their sleep throughout the night, but all that data was previously tucked away in a static PDF report.
I worked on bringing those insights into the app, turning a complex set of sleep biomarkers into something people could actually explore and understand.
Overview · From data to understanding
SleepFit uses a chest-worn device to track what happens while you sleep, capturing a range of sleep, respiratory and cardiac biomarkers. I worked on turning the existing PDF-based sleep report into an interactive in-app experience, making the data easier to explore and understand.
The goal wasn’t simply to move the report from PDF to app. It was to rethink how complex sleep data could be structured, visualised and presented in a way that actually made sense to a consumer.
Problem · Too much, too little
SleepFit already had a lot of useful data, but users had to go through a 37 to 40 page PDF to make sense of their night. Each biomarker was given roughly the same amount of space, with a visual, a long definition and additional interpretation, making the report feel more like a technical document than something designed for everyday use.
From our user research, one thing came through quite clearly. People wanted to interact with their sleep data, not just read through pages of it. The challenge was figuring out how to make all that information useful without making the experience feel even more overwhelming.
From our user research, one thing came through quite clearly. People wanted to interact with their sleep data, not just read through pages of it. The challenge was figuring out how to make all that information useful without making the experience feel even more overwhelming.
Insights · What actually matters?
Going through the existing report made one thing clear to me: not every piece of sleep data needs the same amount of attention. Users needed a clear starting point, with the option to go deeper when they wanted to understand something in more detail.
This shaped the hierarchy of the experience. Sleep health became the primary focus, followed by respiratory and cardiac insights, while related biomarkers were brought together so users could understand how different parts of their sleep connected.
The morning view
The first thing users see after completing a sleep session is a consolidated view of the previous night. I wanted this screen to answer the most basic question first: how did I sleep?
So I brought the sleep score, sleep quantity and a few of the most relevant biomarkers together in one place. This gave users a quick read on their night without having to navigate through individual metrics.
The biomarker view
Once users wanted to look deeper, they could explore their biomarkers across Sleep, Cardiac and Respiratory. Instead of presenting them as one long list, I grouped related information together and created a consistent structure for each category.
The time view
I introduced day, week and month views so users could move between a single night's data and longer-term patterns. The same biomarkers could be explored across different timeframes, making the experience useful beyond the morning after a single sleep session.
Impact · From reading to engaging
From static to interactiveUsers could explore their sleep data directly inside the product rather than downloading a PDF.
From one-way delivery to measurable behaviourThe app created visibility into which parts of the sleep experience users actually engaged with.
From isolated reports to longitudinal trackingDay, week and month views allowed users to understand their sleep as a pattern over time.
- 72%Users opened their sleep report
- 48%Explored at least one detailed biomarker
- 31%Returned to view their weekly sleep trends
Reflection · Making data feel human
For me, the most rewarding part was taking something that felt technical and dense and turning it into an experience that felt approachable. It changed the way I think about designing products where the data is complex, but the person using it shouldn't have to be.
I can’t fit everything I worked on into one case study. If you’d like to dig a little deeper into the project, feel free to reach out.