harmoney
A mobile app that helps couples see household money in one shared view and make decisions from the same facts.
Money gets messy fast when you're sharing a life with someone. Different banks, different cards, different ideas about what counts as a household expense. You end up comparing apps, rebuilding spreadsheets, or just guessing.
Harmoney is what I'm building to fix that. It's a mobile-first app for couples: one shared source of truth for household money. Connect your accounts, see spending together, fix what the system got wrong, and compare what actually happened with what you planned in your Budget.
It's not a bank dashboard. It's not personal finance with a "partner mode" bolted on. It's built around the household as the unit, not two separate silos that kind of sync.
The loop it's built around
The idea is simple:
- Partners connect their accounts
- Harmoney imports and normalizes the activity
- Both of you see the same household view
- Either of you can correct categories and meaning
- The Budget reflects that same data
- You decide what to do next from shared facts, not parallel spreadsheets
What I'm trying to get right
A few things matter a lot to me:
- One shared truth. The feed, summaries, and Budget should agree. No hidden second ledger in the UI.
- Automation you can trust. Import and categorization should save work, but failures and uncertainty need to stay visible. You can always correct what the system misunderstood.
- Calm enough for hard conversations. This is sensitive data. The app should feel precise and trustworthy, not gamified or judgmental about whether you're "good with money."
- Unequal contributions, handled honestly. Not every couple splits 50/50. The Budget supports explicit contribution shares without pretending everyone contributes the same way.
How it's built
Harmoney is a private project still in active development. Stack-wise:
- Mobile: React Native and Expo (TypeScript)
- Backend: Node.js API with Fastify
- Data and auth: Supabase (Postgres)
The mobile app is the daily interface. The API handles household flows, bank connections, and provider orchestration behind the backend. Canonical state lives in the database with household isolation enforced at that layer, not just in the UI.