A reason to save
Helping user set a goal to motivate them to get there by any means possible.
Research method
Researched by observation
People will tell you what they would spend. A game shows you what they do.
I designed a game to observe how people spend and how it makes them feel. The only decision the game ever asks is if you want to spend now or later, and that is the whole point.
I made it simple by splitting it into wants and needs, making it easy.
Design rationale
Spending needs context.
Most finance apps show a number and leave the judgement to you without actual context and that was the problem.
Colour carries direction.
Category hue → white hinge → one fixed spend orange. Income stays flat green.
Every category rolls up into Wants or Needs, and it is that split rather than the raw category that the budget tracks.
Onboarding
Asking questions, to understand them.
Savings get easy when someone helps. Lekka is what will help you, so it is designed to ask the user what they can put aside and what they earn.
Familiarity Building
The colour split is taught earlier so someone can understand the UI early on.
System behaviour
One entry. Every view.
One ledger, and the parts that only make sense moving.
One array of transactions drives every screen. Nothing is precomputed or duplicated per view, which is why the daily hero, the signed nets, the bucket breakdowns and the category rankings can never disagree. The card flips in place rather than pushing a second screen, so the balances underneath never leave and never have to be recalculated.
Keep the context in place.
Implementation and status
Built as a prototype
The first build was a Figma screen look with just visual design.
However, I built it with native Swift elements to make sure the accessibility and familiarity with the OS’s native language guides them and makes it easier.
Personal project · Prototyping.