
Birdget today: the beta in daily use, in dark and light mode.
Birdget is a one-person client project: a native iOS expense tracker built around one specific person's needs. I own it end to end, from the first requirements meeting to the app running on the client's iPhone.
A client asked me to design and build an expense tracker for them. They wanted to set a monthly budget, see where their money actually goes, and learn to handle it better. They had tried several apps from the App Store, but none covered everything they needed, and all of them failed at the same point: to log one expense they had to open the app, tap plus, type the amount, name it, pick a category and a date. After a few days they simply stopped.
The real problem wasn't missing features, it was friction. The client wanted to open the app to look at their finances, not every time they spent money.
Logging without opening the app was the hardest part, so I proposed the rules before designing anything:
A Siri Shortcut and a Quick Entry field, both taking one line like "Coop 50".
Each category holds shortcut words. Add "Aldi" to Groceries once, and "Aldi 50" is filed there from then on. Predictable and fully under the client's control.
Quick entries are dated today, or yesterday if they say so. Older dates are edited in the list.
Amount, title, category and date, for when they want to enter everything by hand.
The client agreed right away: logging stays fast, and the data stays clean enough for a useful overview.
I designed the first draft in dark mode as a low-fidelity clickable prototype, focused on which screens connect and what lives where: a dashboard, the expense form, monthly and per-category budgets, insights, and category management with shortcut words.
One detail came straight from the client: the budget line in the dashboard graph rises linearly across the month, from zero to the full budget on the last day. It shows how much they should have spent by today to stay on track. As long as the actual spending line stays below it, they're on pace; if it crosses it, they're spending faster than their budget allows, even if the month isn't over yet. The idea is to stay within budget the whole month, not only notice at the end.






The first Figma draft: dashboard, expense form, monthly and category budgets, insights, and category shortcuts.
The feedback on the overall idea and look was very positive, with three changes:





I built the app in Swift and Xcode and installed it directly on the client's iPhone for testing. Fast logging works in three places:
Both shortcuts run from Siri ("Log an expense in Birdget"), the Shortcuts app, the Action Button or Back Tap, so they can pick whichever trigger fits their day. Shortcuts turned out to be the client's favorite part of the app.




Birdget in the Shortcuts app, a one-line Log Expense, the step-by-step Add Expense, and the keyword setup behind the automatic categories.
AI: Turned my rules for budget pacing, category totals and keyword matching into Swift code.Me: Defined what every number means and how edge cases behave, then checked each version against test data.I'm a designer and frontend developer, not a backend engineer. For the app's logic and calculations, like budget pacing, category totals and keyword matching, I worked with an AI coding agent: I defined what the numbers had to mean and how edge cases should behave, and checked the results against test data before handing each version to the client.
After a few days of real use we sat down again. Two points only surfaced once their actual spending was in the app:


The expense list with search, category filters and multi-select, where a settle-up counts as income (+€90), and the entry form's expense / income switch.
When I showed the app to a collegue who was looking for a similar tracker, the linear budget line didn't make sense to them at all. They read a budget as a cap: a horizontal line at the budget amount, with spending climbing toward it.
Both readings are valid, they just answer different questions. After discussing it with the client, I made the graph card swipeable with three views:



One swipeable card, three ways of reading the same budget: pace line, budget cap and progress ring.
The point of the app isn't to record spending, it's to change it. So Birdget flags problems while there's still time to react: the monthly view projects where the month will end based on their daily spending rate, category budgets turn orange when they get close to the limit and red once they're over, and Insights calls out every category that went over.
Once the overall budget is exceeded, the whole app switches to red: the status on the dashboard, the spending line in the graph, and the monthly budget with its projected outcome. There's no way to miss it, even with a quick glance.



Over budget on the dashboard and in the monthly view, and saving advice in Insights for every category over its budget.
The client asked for a dark interface, so the Figma design was done dark-first. Once they used the real app every day, they preferred light mode. The app now follows the system setting or can be set to light or dark in Settings, and the app screenshots on this page show light mode, the way it's actually used. The dark theme stays close to the original Figma design.







Appearance setting: System, Light or Dark.
Birdget is in its second testing phase. Since September 2026 the client has used it daily as their only expense tracker and collects feedback as it comes up; critical bugs are fixed right away. At the end of this round we go through everything together and decide on the next iteration. Once it runs smoothly, the goal is an App Store release, so others with the same problem can use it too.
Features and nice add-ons can look valuable on paper, but every extra step is friction. If logging takes effort, people stop using the app, so sometimes the simpler version is the better one.
Instead of balancing the needs of a user group, every decision followed one real person’s habits and preferences. That needs a different focus than designing from personas.
A style that works well in one app doesn’t automatically work in another: the client asked for dark mode but lived in light mode. Showing several versions early keeps the client open instead of putting them off.
Birdget stores all data locally on your device. No personal information is collected, transmitted, or shared. The app does not use third-party analytics or advertising. If cloud synchronization is added in a future update, this policy will be updated.
© 2026 Victoria Zeillinger · Impressum