Health, home and travel decision

Luma

A capable technical user can build the core offline journaling and guided CBT flows in a few weeks, but reproducing cross‑device sync, App Store distribution polish, and the full commercial product experience (subscriptions, ongoing UX, brand/audience) is non‑trivial.

View on the App Store
You pay

$1.99/mo

$24/yr

Per seat. Read off the official pricing page.

You’d pay instead

$100one-off70 h to build

$0/mo3 h/mo upkeep

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

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 opens app → log a worry (text fields + metadata) → run the WorryTree problem‑solving flow (guided prompts) or use sensory practice (audio/timers) → save encrypted local journal entry → review history and simple stats.

What it still won’t have

  • Cross‑device synced experience and the complexity of true end‑to‑end encrypted multi‑device sync
  • App Store audience, reviews, and brand presence
  • Polish and ongoing small‑team product iteration (UX tweaks driven by users)
  • Built‑in community/blog integrations and any paid features tied to a central account service

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 5 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 single‑device iOS journaling app in SwiftUI + Combine using encrypted CoreData (SQLCipher) for local storage. Implement: (1) screens for adding a worry entry (title, context, severity), (2) a guided WorryTree/problem‑solving flow as stepwise forms with state saved to the encrypted store, (3) gratitude and uncertainty tracker screens, (4) audio playback for sensory practices with bundled assets, (5) App Store in‑app subscription plumbing (storekit) to gate premium features, (6) unit and UI tests, error handling, and basic analytics (privacy‑preserving). Out of scope: multi‑device E2E sync, server backend, account management. Include CI, automated tests, and handling of encryption key backup/restore instructions for users.
How we checked1 sources · 3/3 runs agreed · evidence score 59

How the score was reached

  • Partly verdict base52
  • Price verified on pricing page+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 · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded