Tracket
2024
Designed in Figma, built in SwiftUI and live on the App Store.

Role
UX/UI Designer and iOS developer (SwiftUI)
Duration
September to December 2024 for design
Services
iOS
Category
Fintech
Overview
A budgeting app that does not want your bank login
Most finance apps feel like spreadsheets, and many insist on a bank sync. I researched, designed and tested Tracket, then built it in SwiftUI and shipped it to the App Store.
The Impact
From the research and the moderated test. Not from App Store rankings.
23
people surveyed
Aged 20 to 65 and older
3
personas
Kevin, Jane and Doug
5/5
tasks completed
Moderated think-aloud testing
Problem
Clear, motivating, and respectful of people's data
People want to manage their money and get put off by clutter, a mandatory bank sync and no flexibility. The question was how to make a budgeting app that is clear, motivating and leaves the bank login alone.

01
A spreadsheet in disguise
A cluttered interface makes a simple expense feel like work.
02
Bank sync as the price of entry
Privacy-minded people will not hand over account access.
03
Categories that are not theirs
One person's Tech and Gear is another's Emergency Chocolate.
Research
A survey, then three people to design for
I surveyed 23 people aged 20 to 65 and older, and followed up with interviews. Most people already tracked manually. Privacy was non-negotiable. Visual summaries beat long lists.

23 people
A survey, from age 20 to 65 and older.
Interviews
Follow-ups that became three personas.
Five tasks
Onboarding, an expense, a budget, insights, settings.
What we learned
Kevin is 23, a student and a freelancer. Jane is 38 and curbing impulse spending. Doug is 67, retired and cautious with technology. Designing for Doug and Kevin at once pushed the product past my own habits.
The Hide Balance toggle alone sold me.
Usability test participant
Tracket
Organizing recurring patterns and behaviors
Manual tracking, categories people name themselves, and a calmer visual summary showed up together. Hide Balance came from the moment someone else can see the screen.

Key insights
No accounts, and no bank sync.
Colour-tagged categories people can name themselves.
Expense entry belongs at the bottom, for one thumb.
Profile and settings were one place, not two.
Understanding the user journey
Open it, add something, hide the number on a commute, and trust it without connecting a bank.
01
Open the app
Friction
A finance home screen can look like a spreadsheet.
Opportunity
A visual summary, soft shadows, rounded corners, dark mode and accessible contrast.
Impact
The first screen is a budget, not a table.
02
Add an expense
Friction
The first workshop showed entry was awkward with one hand.
Opportunity
Move entry to the bottom and refine the navigation.
Impact
One thumb, on a commute.
03
Hide the balance
Friction
Someone nearby can see the screen.
Opportunity
A Hide Balance toggle.
Impact
The number is there when you want it.
04
Trust it with nothing
Friction
Privacy was non-negotiable in the interviews.
Opportunity
No accounts and no bank sync. Manual tracking first.
Impact
People who will not connect a bank can still use it.
Ideation
Manual tracking first
I refused the obvious finance-app move, connecting the bank, because the research said that was the reason people would leave.

The three personas, the one-handed entry change, and the build beside the design.
01
No accounts
Privacy-conscious people are not asked to hand over bank access.
02
Custom categories
Colour-tagged categories, plus a Hide Balance toggle.
03
Calm, not clinical
Soft shadows, rounded corners, dark mode, and contrast that holds.
Testing interaction flows early
Moderated think-aloud sessions, in person and remote, across five tasks: onboarding, adding an expense, setting a budget, viewing insights and adjusting settings. Participants completed all five. After the first workshop I moved expense entry to the bottom.


Designs
Designed in Figma, built in SwiftUI
I liked it enough to build it. Tracket is written in SwiftUI and it is live on the App Store. Building it exposed empty states, edge cases and messy data.

The design next to the finished build.

Kevin, Jane and Doug, from the survey and the interviews.

Five tasks in moderated testing, then the one-thumb entry change.
Lessons
Doug and Kevin do not share a commute
Designing for both pushed the work past my own use case. Shipping it meant the design had to survive empty states and messy data, not only the Figma frame.
Key outcomes
A live App Store app
Designed, built in SwiftUI, and shipped.
Research with range
23 people, then three personas from 23 to 67.
A test that held
All five tasks completed in moderated sessions.
Privacy as a product decision
No accounts, no bank sync, manual tracking.
