Build or Skip

local-first health data apps

We said SKIP on August 16, 2026. Not settled — due August 16, 2027.

Read this with the caveat. We tested the engine that produced this verdict against 292 launches whose outcomes we already knew, and could not show it predicted which survived. Some of its data sources were also dead at the time of scoring. The verdict stays up, dated and unedited, because a record you can quietly revise is not a record — but it is worth less than it looked when it was written.

Demand for the specific local-first health angle is unproven — every social channel is quiet and keywords are flat, while the paying competitors validate general health tracking, not this wedge. Combined with giant incumbents, real interop engineering, and no reachable buyer channel, the evidence adds up to a SKIP for a solo founder starting from zero.

Was there demand

3out of 10

Social signal is essentially absent (0 Reddit posts, 2 HN posts scoring 9 and 1 points) and search demand is flat with no strong keywords. The big competitors prove demand for health tracking broadly, but none charge for the specific 'local-first' wedge, so paid-competitor evidence doesn't transfer.

Could a builder win it

4out of 10

A clean privacy/local-first wedge exists, but the primary incumbents are funded giants (Apple, Google) with platform network effects, and health-data interoperability (FHIR/HL7) carries real regulatory and engineering weight. Worse, there's no obvious organic channel to reach buyers who aren't already asking for this.

The case against this verdict

The strongest case FOR building: local-first is a genuine philosophical wedge no incumbent will follow (their business models depend on cloud data), and the audited open-source privacy angle could earn organic trust-driven distribution the giants structurally cannot match. If regulatory tailwinds around data ownership grow, an early, credible local-first health app could own a defensible niche cheaply.

Who was already there

  • Apple HealthClosed ecosystem, limited interoperability, poor data export, iOS-only for full features
  • Google FitData privacy concerns, limited local-first capabilities, requires Google account
  • Oura RingRequires proprietary hardware, subscription model, limited scope (not full health data)
  • Open mHealthLimited UI/UX, low consumer awareness, sparse mobile apps, developer-focused
  • Obsidian Sync (health notes)Not health-specific, steep learning curve, no medical interop, requires self-setup

Other verdicts

What is worth more than this page. The register records what became of 6,266 real launches. No engine has to be right for that to be true.