Health, home and travel decision
Debatium
A small technical team or single engineer can reimplement the core question-packs and local app experience, but reproducing the App Store presence, polished UX, localization, and subscription economics that the live product currently benefits from makes a full replacement nontrivial.
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-off80 h to build
$0/mo3 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
- Show a question from a selected pack, let each partner answer or discuss, then advance to the next question; unlock additional packs via App Store in‑app purchases/subscription.
What it still won’t have
- App Store listing, ratings, and existing user base
- Polished UI/UX and iteration the existing app has received (many updates listed)
- Localization into 6 languages (English + 5 more) unless implemented
- Ongoing A/B testing, store analytics, and marketing the paid subscription
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Debatium 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 native iOS app (SwiftUI, iOS 16.4+) that implements: name entry, pack browsing, question view with next/back, local pack content storage (JSON files bundled and optionally downloadable), progress persistence via CoreData, StoreKit-based in‑app purchases and weekly/annual subscription unlocks, and localization support for multiple languages. Out of scope: server backend, social features, analytics beyond local counters. Include error handling for failed purchases, corrupted content, and App Store entitlement checks; provide unit tests for content loading and purchase logic and an App Store build configuration (entitlements, privacy strings, and screenshot export).
How we checked
How the score was reached
- Partly verdict base52
- 3 cited sources+3
- Evidence score55
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.
- official productDebatium - Couple Game Convo - App Store
- official productDebatium - Couple Game Convo - App Store
- official productDebatium - Couple Game Convo - App Store
Integrity checks
What held up, and what did not.
