Your Apple Health data isn't telling you what you think it's telling you

I have worn an Apple Watch since 2018. By the time I started building Observa, Apple Health had eight years of my data: sleep, heart rate, HRV, ECG readings, mindfulness minutes, workout sessions, blood oxygen, walking steadiness, the lot.

I had no idea what any of it meant.

I mean that literally. I could open the Health app, watch a number go up and down, look at a chart shaped like a small mountain range, and still not answer the only question that mattered: should I do anything differently this week?

Observa exists to answer that question.

What is Apple Health good at?

Apple Health is excellent at what it’s built for. It collects, normalises, and stores health metrics with privacy guarantees no other consumer system has offered. The charts are well designed, the unit handling is careful, and the data layer is, honestly, the best in the industry.

What Apple Health doesn’t try to do, and in my view shouldn’t, is editorialise. It won’t tell you that your HRV dropped because of last week’s two short nights. It won’t connect your morning resting heart rate to the wine you drank on Saturday. It won’t say, “your training load is twenty percent above your eight-week average and your recovery scores are dropping; consider a deload week.” Apple is right to hold back here. Health data is sensitive, and over-interpretation is a real danger.

For the user, though, that restraint leaves a gap: you have the data and nothing that tells you what it means.

The chart-trance problem

If you’ve ever spent twenty minutes scrolling through a year of HRV measurements looking for a pattern, you know the problem I mean. The brain is bad at spotting patterns in noisy time series. We see trends that aren’t there and miss ones that are. We anchor on the latest measurement. One low reading makes us anxious and one high reading reassures us, and statistically neither means anything.

More willpower won’t fix this, because the problem is the display. A chart with seven hundred data points and no overlay works more like a Rorschach test than a tool.

What Observa does

Observa sits on top of Apple Health and answers a small set of questions directly:

• How recovered am I today, and why? Readiness weighs sleep, HRV, resting heart rate, and training load against your own typical range, and “Why this score?” shows which of them moved it.
• What does my HRV look like against my own baseline? Your baseline, not the population’s. A 38 ms HRV reading means nothing until you know whether your personal baseline is 32 or 56.
• Which habits tend to line up with better sleep and recovery for me? Patterns ranks up to four over 14, 28, or 90 days, each with a confidence label. This is where the interesting stories are, the ones where you say “oh, of course.”
• Is my training load keeping pace with my recovery? Training load compares your last 7 days with your last 28, and “Should I train today?” turns it all into Push, Maintain, Recover, or Rest. If load and recovery diverge, you are building up fatigue, however the individual workouts felt.

None of this is a medical diagnosis. Observa can’t tell you whether you have a clinical sleep disorder, a cardiac issue, or an autoimmune condition, and it won’t pretend to. What it can do is take a year of your own data and turn it into the three or four sentences a thoughtful coach might give you if they had time to read it carefully, which most coaches don’t.

Why this had to be on-device

The other constraint behind Observa is the obvious one: health data should never leave your device.

That’s a statement of values, and it’s also a technical decision with real consequences for the product. A cloud version of Observa could use better correlation models, larger datasets, and more compute. It would also be a target for breaches, a regulatory minefield in several jurisdictions, and, worst of all, something the user couldn’t verify.

Observa’s analysis runs on the device, with rules and statistics simple enough to compute there. It is simpler than what a cloud service could do. In return, nobody but you ever sees a single data point. There is no cloud account to compromise and no database for anyone at Lagerland Apps to look into.

I think that’s the right tradeoff for health data. I know not everyone agrees, and for some uses, such as clinical research and longitudinal population studies, on-device can’t compete. Observa isn’t built for those. It’s the interpretation layer for one person’s own life, and that person owns it.

What this means in practice

If you keep opening the Health app, scrolling, and coming away with nothing, Observa was made for you. It reads what’s already in your Health database (with your permission, limited to the categories you allow) and gives you a morning read in place of a panel of charts.

It won’t tell you what to eat or when to sleep. It will tell you something specific, like “Readiness is Moderate because your resting heart rate is above your usual range,” and leave the decision to you.

That’s the whole product: Apple’s data layer plus a thin layer of honest interpretation, kept on your device and offered without medical claims. It does the modest, useful job the Health app leaves undone.