Where I Started

Most budgeting apps feel either too technical or too limiting. I wanted to explore how I might make money management feel more intuitive, less like a spreadsheet and more like a conversation. I didn't begin with all the answers. Just a core problem to solve and a goal to create something people would actually want to use.

What People Struggled With

I interviewed five people between 28 and 55 to understand how they manage money, what stresses them out, and what they wish budgeting tools did better. Most didn't follow a method. They checked balances, hoped for the best, and felt anxious by the end of the month. Tools that asked for too much manual input got abandoned quickly. What people wanted instead was simple guidance and clarity.

Understanding Competitors

I analyzed 8 popular personal finance apps to understand their features, usability, and design patterns. This research helped identify gaps and opportunities, ensuring Clever Spend offers a simpler, more focused experience that stands out in the market.

From Structure to Screens

Before diving into visuals, I mapped the information architecture and used wireframes to bring clarity to structure and flow. These low-fidelity screens helped me move fast, test ideas early, and collaborate closely with the developer. It was the quickest way to align on direction and spot usability issues before they became expensive.

Building the Visual Language

To keep the interface consistent and development smooth, I built a modular design system from the start. It covered typography, spacing, color, and components, all clearly defined and reused across more than 40 screens. The system became a shared language between design and code, making collaboration faster and handoff easier.

The Final Look

I handled everything from the logo and app icon to the full UI and design system. My focus was on creating something that feels clean and trustworthy but also a bit friendly, because let's be honest, budgets can be intimidating. I kept the visuals consistent across screens and made sure every detail supported a calm, confident experience.

Final Thoughts

This project challenged me in all the right ways. It pushed me to think critically, adapt quickly, and design with both users and developers in mind. When people got confused about savings and debts, I introduced clearer labels and distinct visuals to guide them. Some flows needed to be reworked to align with technical constraints, and the final UI took a few iterations to feel just right.

This process wasn't perfect, but it was iterative, honest, and focused. In the end, I shipped a functional MVP that solves real problems. There's still room for improvement, but for now, this is a solid first step and that's what matters.

Outcomes That Made a Difference