Learning and careers decision

FamilyPoints

A small technical user can recreate the core functionality (tasks, points, schedules, basic AI suggestions) within a week using existing open-source prior art; the main losses are native App Store polish, push notifications, and the vendor's distribution/monetization.

View on the App Store
You pay

$9.99/mo

$120/yr

Read off the official pricing page.

You’d pay instead

$100one-off40 h to build

$25/mo4 h/mo upkeep

On cash alone, building overtakes the subscription at 4 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 FamilyPoints alternatives, with the arithmetic →

What a replacement has to do

  • Create/manage family tasks, assign points, children complete tasks and claim points, optionally have parent or AI approve and redeem rewards

What it still won’t have

  • Native polished iOS App Store distribution and platform-specific UX
  • Built-in push notifications tied to iOS native APIs
  • Existing App Store reviews/visibility and in‑app purchase plumbing
  • Developer-provided backup/sync service and lifetime purchase option

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 4 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 family chore tracker web app using React (frontend), Firebase Auth + Firestore (backend), and Vercel hosting. Core features in scope: family workspaces with parent/child roles; CRUD tasks with point values and recurring schedules; per-user point ledger and history; approval workflow for parent verification; scheduled serverless job to reset recurring tasks; basic backup to Cloud Storage; optional AI Judge endpoint using OpenAI to suggest point allocations. Out of scope: native iOS app packaging and App Store IAP integration. Include input validation, error handling, automated unit tests for core business logic, and deployment scripts.
How we checked2 sources · 2/3 runs agreed · evidence score 87

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 2 cited sources+1
  • Price verified on pricing page+3
  • Evidence score87

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! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded