Health, home and travel decision

Paced breathing exercises zone

A competent mobile developer can reproduce the core guided‑breathing app and local journaling in about a week; there are no durable moats on the App Store page that prevent a rebuild.

View on the App Store
You pay

$13.49/mo

$162/yr

Read off the official pricing page.

You’d pay instead

$100one-off34 h to build

$0/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 1 seat.

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

  • Open app → select breathing technique → follow timed visual/audio cues → session recorded to local journal.

What it still won’t have

  • App Store subscription management and revenue flow (if you don’t publish through App Store)
  • Curated meditation catalogue unless you license or create your own content
  • App Store distribution, ratings, and automatic device updates

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 1 seat.

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‑target iOS app (SwiftUI + Combine) that implements a guided paced‑breathing trainer. Core features in scope: home screen with technique list, selectable breathing patterns, active session UI with animated visual guide, haptic/timer cues, AVFoundation audio playback for optional meditation tracks, local persistence of session records using Core Data, settings screen, and CSV export of session journal. Out of scope: App Store submission and paid subscription billing (implement a local unlock toggle instead). Include proper error handling, unit tests for timer and persistence logic, and basic UI tests for the session flow.
How we checked1 sources · 2/3 runs agreed · evidence score 81

How the score was reached

  • Build verdict base78
  • Price verified on pricing page+3
  • Evidence score81

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! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded