Health, home and travel decision

tortolitos

A competent engineer can reimplement the core flows (Q&A, canvas, photo sharing, streaks) in multi‑week effort; reproducing App Store polish, widgets, billing integration and the existing user base is nontrivial, so keep paying if you need the full product and distribution.

View on the App Store
You pay

$2.08/mo

$25/yr

Read off the official pricing page.

You’d pay instead

$100one-off54 h to build

$30/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 19 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

  • Present question packs to each partner, collect answers, reveal answers once both replied; lightweight shared canvas (real‑time drawing), daily photo sharing, and streak/countdown tracking.

What it still won’t have

  • App Store distribution, reviews, and discoverability
  • Polish around mobile widgets, platform-specific integrations and notifications
  • Existing userbase and community
  • Built-in in-app purchase handling via App Store (would need own billing integration or separate App Store subscription setup)
  • Language/localization and ongoing content additions currently provided by the vendor

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 19 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 minimal couples relationship mobile app using React Native (Expo), Node.js + Express, and PostgreSQL (hosted on Supabase). Core features in scope: email-based sign-up and partner pairing; question packs CRUD and UI; answer submission logic that hides answers until both partners respond; realtime shared canvas using WebSockets (Socket.io) or Supabase Realtime; photo upload to Supabase Storage with per-couple feed; daily streak and countdown logic (server cron + simple endpoints); basic subscription gating (Stripe) to lock premium packs. Out of scope: App Store submission and platform-specific widgets, advanced animations, localization beyond English/Spanish, extensive analytics. Include input validation, error handling, unit tests for backend endpoints, and end-to-end tests for the main flows.
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