Redesigning EarlyCue

March 2026

EarlyCue is a mobile app that detects inflammation before you feel sick. It works on an algorithm that combines data from wearables and user input to identify illness days before symptoms appear.

I first worked on EarlyCue during its discovery phase. We interviewed COPD patients and designed the first version of the app specifically for people managing chronic disease. The focus was to help patients and their providers catch flare-ups early to reduce their severity.

The discovery went well and a first MVP was released.

Fast forward to early 2026, I was contacted to work on a new version of the product: A Japanese pharmaceutical company wanted to pilot the app with their corporate employees and suggest using their products if illness was detected.

This meant the app was no longer just for COPD patients. It needed to feel like something you'd want to open every morning, not like a medical device.

The timeline was very tight. I had seven days to redesign the experience, with usable designs needed by day three or four so development could start immediately. The pilot launch was roughly a month out.

Understanding where we were at

One of the main problems I identified as soon as I began the sprint was that the app had grown reactively. What I mean by this is that without clear product direction, new features had been appended in a way that made the app feel “patchworked” or lacking intention.

In practice, each feature (e.g. syncing data, prompting questionnaires, collecting daily check-ins) lived as its own card on the home screen. These cards stacked vertically and could end up pushing your Immune Activity status - core value of the app- below the fold.

[VIDEO: V1 home screen showing the stacked cards / alert layers]

There were other things to address too:

The app needs a week of data before the algorithm can establish a baseline. This is common in many health tracking apps, and the empty states are usually handled by a progressive introduction into the features of the app. This adds interest and gives the user a base motivation to continue returning over time.

quote growth design introduction psychology). Example of other apps - credit mobbin

EarlyCue’s calibration period had generic copy("Unlock amazing features") and a confusing “completed” state which did not provide concrete feedback.

Finally, the most common feedback from early testers was blunt: why do I need this if I already have the Oura app?

[IMAGE: V1 onboarding screens with generic copy and illustrations]

I started by writing down everything that needed attention. And I mean everything - from email design to API latencies. I could prioritize later.

An external audit had already flagged about ten items, ranging from broken layouts on certain phones to confusing date displays.

As I went through an ever-growing list of fixes, a bigger question came to mind: What is EarlyCue’s actual value proposition, and how do you make someone care about an immune score they've never heard of?

[IMAGE: The audit list / scope document, or a screenshot of the initial requirements]