Health, home and travel decision

Lovii

A competent developer can build a useful subset (messaging, shared pet, daily challenges, widgets) in a few months, but reproducing the full App Store product polish, multi-device widget behavior, and subscription/paywall refinements is non-trivial — so build a narrow replacement or keep paying for the full app.

View on the App Store
You pay

$5.99/mo

$72/yr

Read off the official pricing page.

You’d pay instead

$100one-off144 h to build

$50/mo6 h/mo upkeep

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

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Lovii alternatives, with the arithmetic →

What a replacement has to do

  • Partners pair accounts → exchange messages, love letters, and photos → complete daily challenges and mini-games → care for a shared virtual pet/plant whose state syncs between devices → view/update shared widgets and reminders.

What it still won’t have

  • App Store distribution polish, review handling, and established UX polish
  • Existing user base and retention optimizations
  • Marketing, analytics history and tuned prompts for daily challenges
  • Platform-specific refinements (widgets, lock-screen realtime) and ongoing App Store paywall handling

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 10 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 iOS couples app using SwiftUI for the client and Firebase (Authentication, Firestore, Cloud Functions, Cloud Storage) for the backend. In scope: email auth and partner-pairing via invite codes, a private messaging screen supporting text and photo messages, a shared document in Firestore representing a virtual pet/plant with care actions and simple sync/conflict resolution, a small daily-challenge engine (deliver questions, store responses, mark rewards), home-screen widget integration reflecting shared pet state, and App Store in-app subscription handling including receipt validation via Cloud Functions. Out of scope: native Android client, advanced mini-games, ML personalization, marketing/analytics beyond basic event logging. Include error handling, unit tests for backend functions, UI tests for core flows, and CI to run tests and deploy Cloud Functions.
How we checked2 sources · 3/3 runs agreed · evidence score 65

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 2 cited sources+1
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score65

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 · 2

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