What would a longevity app look like if the goal were not to collect more data, but to make better use of the minimum data that actually helps?
Longevity information is abundant. Translation is harder. Training, nutrition, recovery and prevention advice often arrives as isolated recommendations, usually without enough context about the person trying to use it.
I wanted to explore what happens when that research has to become an actual interface: something opinionated enough to be useful, but restrained enough not to turn everyday health into another surveillance dashboard.
The interface became the test. Every screen forced a choice about what deserves attention, what should adapt, what should stay quiet — and what data never needed to leave the device in the first place.
The onboarding asks the things that actually change the training prescription: how familiar you are with strength training, what matters most right now and the practical constraints around your week.
The point is not to collect a richer profile. It is to collect only enough information to make the next decision better.
There is a workout to do. There is the week around it. There are a few fundamentals — protein, fibre and sleep — that are useful precisely because they are boring enough to matter repeatedly.
The 12-week plan sits underneath that daily view, but the app does not ask you to manage a miniature health operating system just to know what to do today.
The workout view is intentionally practical: the movement, the prescription, the weight and reps, and a way to swap something when reality disagrees with the plan.
Afterwards, progress is reflected back without turning consistency into a punishment system. The completion screen literally says consistency > streaks. Missing a day does not reset your life.
The health area surfaces a small set of foundations and the next useful action — for example knowing your blood pressure — without collapsing everything into a single longevity number.
And the privacy choice is visible in the product itself: the prototype keeps its profile, plan history, workouts, health baseline and check-ins locally in the browser, with a one-click option to delete all local data.
Prototypes force choices that research can postpone. What should the app know about you? What actually needs to be stored? How much personalisation earns its complexity? Which behaviours deserve tracking, and which merely make the dashboard look busier?
Future You sits alongside a separate longevity research project where I collect and structure the evidence that informs this work.
The hardest design problem was not adding capability. It was deciding where capability stopped being worth its data, cognitive or interface cost.
The prototype became less about “a longevity app” and more about a broader question I keep coming back to: how do we turn research into something people can actually use without flattening uncertainty or collecting everything just because we can?