Budget
Tracker
A personal finance app that puts logging front and center. The best budget app is the one you actually use.
The Problem
Every budget app my wife and I tried had the same issue: logging a transaction was buried behind multiple taps, menus, and screens. By the time you navigated there, you'd already lost motivation.
On top of that, most apps require connecting your bank account. Handing over credentials to a third-party service never felt right.
I wanted something simple: open the app, log the transaction, done. No bank connections, no syncing, no friction.
The Approach
I started with a Design OS: a set of tokens, components, and layout primitives to establish the visual foundation quickly and consistently.
From there, I built it as a Progressive Web App so it feels native on any phone without the friction of an app store. All data stays local on the device.
I used Claude Code throughout, from scaffolding the app to building features. It was a real test of what's possible when a designer codes with AI assistance.
Key Features
Instant Transaction Logging
The home screen opens directly to Log Transaction. Type naturally ("Spent 500 on lunch") or expand the manual form for full control over amount, category, and date.
Personal & Joint Accounts
Switch between personal and joint accounts with a single tap. My wife and I track shared household expenses separately from individual spending.
Transaction History & Export
Monthly breakdowns with opening/closing balances. Export any date range (current month, last quarter, or custom) as a file for your records.
AI-Powered Insights
A dashboard with spending breakdowns and a chat assistant powered by Groq AI. Ask questions like "How much did I spend on food this month?" and get instant answers.
Customizable & Private
Dark, light, and system themes. Groq API key stays on your device. All data stored locally with no servers, no bank connections, and no tracking.
What I Learned
Building this taught me that the best way to understand users is to be one. Every design decision was tested by daily use. If something felt slow or awkward, I fixed it immediately.
Working with AI (Claude Code) as a build partner was eye-opening. The Design OS gave me a consistent visual language from the start, and AI handled the implementation plumbing. My role was the same as always: deciding what to build, how it should feel, and when something wasn't right.
The biggest takeaway? Solving your own problem is the purest form of user-centered design.