Case study, Self-initiated, 2026
Budget Tracker
A budgeting app organized around priorities, what to fund first, instead of rigid category buckets. I designed and built it end to end and shipped it: live on the App Store, in beta on Play Store. The most useful lessons came from the last 10%, getting an accepted build, and the fixes that only surfaced once real people used it.
- Role
- Design & build
- Timeline
- 2026
- Disciplines
- Mobile App, Web App, Product Design, Front-end
01Why I made it
Most budgeting apps force your money into rigid categories, then make you feel behind when real life doesn't match. I wanted one built around priorities, what to fund first, and I wanted to actually ship it, not stop at a prototype.
02What I built
A priority-based budgeting app, recurring bills, reminders, and a “safe to spend” view, live on the App Store and in beta on Play Store. I designed and built the whole thing, down to a reusable Settings pattern (a row that opens a bottom sheet) shared across the app.
- Priorities first, not fixed category buckets
- Recurring bills and reminders
- One Settings pattern reused across Currency, Appearance, and more
03The last 10% is the real work
The gap between a working demo and an accepted build is where the actual effort lives, an Apple rejection over a closed version train, platform limits, and the small fixes that only show up once real people use it (a toggle that read white instead of iOS green, a label that wrapped to two lines). None of those fixes needed new ideas; they needed me to hold to the system I'd already built.
+Gallery
The hard part of shipping isn't making new decisions, it's holding to the ones you already made. The visible “wins” were really the system catching me when I drifted from it.
What I took from it
Next
Prodelity