Skip to content
In development

FamilyFolds

FamilyFolds is an app for running a household. A parent assigns a chore, a child completes it, a parent approves it, and points enter a ledger the server keeps; points are spent on rewards. Around that loop sit family chat, shared notes, live location that shows who is looking, and a password vault.

The app is built — chores, ledger, rewards, vault, live location and chat are in, with Clerk sign-in. What remains is release work: production data setup, real-device testing and store listings. It is not publicly available yet.

FamilyFolds
iOSAndroidWebDesktop

[In the box]

What it actually does

  • Assign → complete → approve → points → reward, as a single loop
  • Append-only point ledger the server owns end to end
  • Zero-knowledge password vault with per-item PIN escalation
  • Live location sharing that always shows who is looking
  • Notes, checklists and a merged family calendar
  • Roles for parent, teen, child and extended family
iOSAndroidWebDesktop

By the numbers

Status
Built — beta preparation
App
Flutter, Android + iOS
Backend
Cloudflare Workers + D1 (18 migrations)
Sign-in
Clerk (OIDC)
Ledger
Append-only, D1 + Durable Object
Point bounds
0 – 1000
Badge tiers
4 (Bronze → Platinum)
Location history TTL
24 hours (default)
Accessibility target
WCAG 2.2 AA
Battery budget
< 3% / day
Target MVP
~5 months

[Features]

Inside FamilyFolds

Every item below is implemented in the codebase, not planned for a future release.

Chores with a real state machine

draft → assigned → accepted → in_progress → submitted → approved/rejected → done, with photo proof, reason-required rejection, subtasks and overdue escalation.

Schedules, rotation and streaks

Daily, weekday, weekly, interval and rotating schedules with a fairness view, a template library, swaps, vacation pause and streak bonuses.

Server-authoritative points

Points only ever enter through an append-only ledger written by the Durable Object that coordinates the family — never straight from a client.

Reward store with escrow

Points are held while a redemption is pending approval, refunded on failure, and the system can never issue debt.

Transparent location

MapLibre live map with three sharing frequencies, named geofences, check-in requests, trip sessions and a 30-minute teen ghost mode.

Zero-knowledge vault

A 256-bit family vault key wrapped per member with X25519, items sealed with XChaCha20-Poly1305, HaveIBeenPwned breach checks and a printable recovery kit.

Family chat with review

A family room, custom channels and DMs with reactions, voice notes, read receipts, threading, pins, quiet hours and a parent approval queue for kid-uploaded images.

Notes and boards

Family, member and custom boards with LWW-synced checklists, free-form notes, six templates, item-to-task conversion and PDF export.

[Architecture]

How it is built.

The decisions that shaped the codebase, and what each one buys.

01

One Durable Object per family

FamilyCoordinator serialises submissions and approvals so two parents approving at once cannot race the ledger. It is the single writer by design.

02

Ledger reconciled by queue

The Durable Object emits events, a queue consumer reconciles them into D1 with INSERT OR IGNORE idempotency, and a cron sweeps every fifteen minutes.

03

Keys that never leave the device

The vault is zero-knowledge: keys are wrapped per member and never leave the device. Attachments and proofs go to an R2 bucket behind signed access.

04

Design guardrails as testable rules

Never colour as the only state signal. Never white text on yellow. Never coral for destructive actions. Never colour alone. These are written into the design system, not left to taste.

[Who it is for]

Built for

  • Organiser parents (30–50) who own the mental load
  • Busy parents who want check-ins without arguments
  • Teens (13–17) who want their own space in the family app
  • Kids (6–12) who want big buttons and instant reward
  • Grandparents and extended family who mostly read

[Non-negotiables]

The rules we held

  • No penalty points in v1 — the design refuses to be punitive
  • Leaderboards are off by default, because competition between siblings backfires for many families
  • Location sharing is always transparent: members can see who is viewing them
  • Never run ads, never charge per child

[Stack]

Built with

FlutterDartMaterial 3 (customised)Cloudflare WorkersD1Durable ObjectsQueuesR2OIDC / JWKSdesign tokens (JSON + CSS)

Delivered

  • The full chore loop: assign, complete, approve, points, reward
  • Append-only points ledger, written by the server only
  • Reward store with escrow and redemption
  • Zero-knowledge password vault
  • Live location with geofences, and transparency about who is viewing
  • Family chat, shared notes and boards
  • Clerk sign-in (OIDC) with silent refresh

Not done yet

Listed rather than hidden.

  • Production database setup and worker deployment
  • Real-device testing: location accuracy, geofences, battery
  • Play Store and TestFlight listings, privacy policy page
  • Security review of the vault and location features before beta

[Timeline]

How it got here.

Where this came from, in order.

    1

    Phase 0

    Decide what it is not

    Penalty points were cut from v1 on trust grounds, and the leaderboard was made opt-in because competition between siblings backfires for many families.

    2

    Phase 0

    Design system and token set

    Five theme packs where canvas, ink, primary action, secondary action and focus move together — four atmospheres plus dark.

    3

    Phase 0–1

    Backend contracts

    Five endpoints, one Durable Object per family, an idempotent queue consumer and a D1 ledger that reconciles without double-counting.

    4

    Now

    Beta preparation

    The feature set closed in October 2026 — vault, location and polish phases done, Clerk sign-in in. The remaining work is production setup, device testing and store listings.

[FAQ]

Common questions.

The questions we would expect to be asked.

Is it finished?

The app is. What is left is release work, and it is mostly on us rather than in the code: production data, a worker deployment, testing location on real phones over real days, and the store listings.

What does FamilyFolds cost?

The plan is Free for a family of six with chat, chores, points, the store, twenty vault items and 24-hour location history. FamilyFolds+ is proposed at roughly $4–6 per month for unlimited vault storage, attachments, autofill, 30-day location history and weekly review reports. It is a proposal, not a shipped plan — there is no pricing page and no checkout.

Why no ads?

Ads do not belong in a family app. Same reason we never price per child — per-child pricing feels like a tax on family size.

Can I use it now?

Not yet. It is in beta preparation and there is no public sign-up. The contact page is the way to ask about beta access.

[Contact]

Questions about FamilyFolds?

Want to know more about FamilyFolds — timelines, availability or how it works under the hood? Send us a note.