The buildFlutter · shared realtime state · iOS and Android
01
The problem
Expense splitters were designed for trips: a group forms, spends, settles, and dissolves. A household never dissolves. Rent recurs, groceries rotate, chores drift, and the apps built for holidays make ongoing life feel like an accounting exercise.
02
The decisions
One running balance per household instead of a ledger of micro-debts, recurring bills as first-class citizens, and a settle up that nudges rather than invoices. The shared grocery list lives next to the money because that is how households actually operate.
03
The outcome
In design, with the core balance model and recurring-bill engine already prototyped. Next in the build queue after PhotoSweep ships.



