Health, home and travel decision

lovelee

A competent developer can build a useful, narrower version of lovelee (pairing, messages, doodles, shared state) in a multi-week effort, but reproducing the polished mobile UX, App Store distribution, and continued operational polish of the paid product makes keeping the commercial offering reasonable.

Visit website
SubscriptionCustom pricing
Initial build52 hours
Monthly upkeep6 hours + $40
Evidence3/3 runs agree

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 lovelee alternatives, with the arithmetic →

What a replacement has to do

  • Two partners pair an account, exchange love letters/doodles and quick affection signals, and see shared state (pet, plant, heart points) update over time.

What it still won’t have

  • Polish and mobile UX quality (animations, polished doodle tools)
  • App Store submission, review, and store-level discovery
  • Advanced analytics and growth/engagement tooling
  • Any proprietary content, community trust, and brand presence
  • Managed premium subscription handling and fraud mitigation

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

lovelee 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

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 mobile app using React Native for the client, Node.js + Express for the API, Postgres for relational data, S3-compatible storage for doodle images, and Firebase Cloud Messaging / APNs for push. Core features in scope: account signup and partner pairing via invite link, send/receive text love letters and upload simple doodles (PNG), a shared JSON-backed "home" state (virtual pet level, heart points) with endpoints to read and update, daily check-in endpoint and server-scheduled reminder jobs, and a basic React Native UI to view inbox, compose messages with a doodle canvas, and display shared state. Out of scope: payments/subscriptions, app store submission, multi-tenant admin UI, advanced analytics, and in-depth moderation. Include input validation, authentication (JWT), error handling, unit tests for server endpoints, and end-to-end tests for the primary flows (pairing, send message, update pet). Provide deployment scripts for one DigitalOcean or AWS EC2/managed Postgres instance and instructions to wire FCM/APNs credentials.
How we checked2 sources · 3/3 runs agreed · evidence score 62

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score62

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.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded