Health, home and travel decision
Rift: Reality Shifting
A competent technical user can build a narrow, useful replacement (script editor + guided audio) but matching the shipped app's polish, App Store presence, subscription history, and userbase would be expensive and time-consuming.
View on the App Store↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off160 h to build
$0/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
- Author and edit a DR script, save it, run a guided audio shifting session with timers/ambient sounds, and record a shifting journal entry.
What it still won’t have
- Existing App Store listing, reviews, and organic user acquisition
- Polished design and user-facing bug fixes accumulated in the shipped app
- Scale, active userbase, and any proprietary content shown in the app
- Immediate cross-device provisioning and established subscription billing history
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Rift: Reality Shifting 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
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
Build a single-developer iOS app (Swift + SwiftUI) that reproduces the core Rift features: (1) a form-based DR builder with ~25 sections and reusable templates, (2) local persistence plus optional Firestore sync, (3) media uploads and an image gallery using Firebase Storage (or S3), (4) audio-guided shifting sessions with ambient tracks, adjustable timers, and local notifications (AVFoundation + background handling), and (5) simple subscription management via StoreKit and a minimal server endpoint (Node/Express on Heroku or Vercel) for receipts. Out of scope: training custom TTS models, complex social features, and an App Store listing. Include error handling for network failures, media upload retries, background audio continuation, and unit/UI tests for the DR editor and session runner.
How we checked
How the score was reached
- Partly verdict base52
- 3/3 assessment runs agreed+4
- Evidence score56
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.
- official productRift: Reality Shifting on the App Store
Integrity checks
What held up, and what did not.
