Health, home and travel decision

jurney

A single technical user can build and operate a useful web replacement (onboarding, logging, analytics, calendar) using existing open-source fitness projects as starting points; the original's App Store distribution, native UX, and any proprietary models would be lost.

View on the App Store
You pay

$4.99/mo

$60/yr

Read off the official pricing page.

You’d pay instead

$100one-off100 h to build

$20/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 6 seats.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All jurney alternatives, with the arithmetic →

What a replacement has to do

  • Ask user onboarding questions to create a plan → log daily weight → compute personalized analytics and trends → display progress on a calendar and past logs.

What it still won’t have

  • App Store distribution and existing install base
  • Polished native iOS UX and OS-level features (push, HealthKit integrations)
  • Built-in in‑app billing and App Store subscription management
  • Any proprietary analytics/modeling used by the original app

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 6 seats.

Paid seatsseats

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 lightweight web replacement for a weight-loss coach app using React (TypeScript) frontend, Node.js (Express) backend, and Postgres. Core features in scope: 1) onboarding questionnaire to capture goals/starting weight/target; 2) user auth (email + password) and profile storage; 3) daily weight logging API and DB schema; 4) analytics service that computes moving averages, weekly/monthly trends, simple forecast, and BMI; 5) progress calendar UI showing daily entries and trend overlays; 6) CSV export of logs. Out of scope: native iOS app, App Store in‑app purchases, image uploads, HealthKit integration, paid subscription billing. Include input validation, server-side error handling, REST API tests (unit and integration), and deployment scripts (Dockerfiles, a small Terraform or docker-compose example) with instructions for hosting on a single small cloud VM. Provide CI tests and basic monitoring (error logs).
How we checked3 sources · 2/3 runs agreed · evidence score 63

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Evidence score63

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.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded