Health, home and travel decision

Health3

A competent developer can reproduce a useful subset (OCR parsing, biomarker mapping, reports, HealthKit import) in a multi-week build, but matching the polished app, curated biomarker content, App Store polish, and ongoing product maintenance makes a full replacement impractical for a single person to sustain long-term.

View on the App Store
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off98 h to build

$50/mo6 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • User uploads a lab-result image or imports clinical records, app OCR/parses values, normalizes biomarkers, stores results, and renders a shareable Test Report with trends and insights.

What it still won’t have

  • Polished mobile UX and onboarding refinements
  • Curated and maintained biomarker library, literature-sourced reference ranges and explanations
  • Ongoing App Store distribution, updates and mobile-specific bug fixes
  • Subscription, trial management and in-app purchase flows already implemented
  • Security, privacy reviews, and continuous clinical data handling improvements

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Health3 does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal Health3-style iOS app and backend using: iOS SwiftUI app + HealthKit for Apple Health import, a small Node.js (Express) API with Postgres for storage, Tesseract (or cloud OCR fallback) for image parsing, and Puppeteer/HTML-to-PDF for report export. In scope: image upload UI, OCR pipeline that extracts labeled biomarker name/value/date, a biomarker canonicalization table with unit conversions, basic trend charts, shareable PDF Test Report, Apple Health import button that maps supported clinical-record biomarkers, user auth (email+password), and one reminder scheduler. Out of scope: subscription/in-app purchase billing, advanced machine-learning document parsers, large-scale analytics, and mobile push notifications. Include error handling for failed parses, unit-mismatch detection, and tests for OCR parsing, biomarker mapping, HealthKit import, and PDF generation.
How we checked3 sources · 3/3 runs agreed · evidence score 59

How the score was reached

  • Partly verdict base52
  • 3 cited sources+3
  • 3/3 assessment runs agreed+4
  • Evidence score59

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded