Budget App

Timeline:
Feb – June 2025
Role:
Lead UXR & Design (solo)
Tools:
Figma, WCAG plug-ins

A research-driven budgeting app for novice and visually impaired users — from competitive analysis and persona development through two rounds of usability testing.

View Prototype →
Animated walkthrough of the Budget App showing the redesigned UI with clean iOS-style layout

Overview

Many budgeting apps overwhelm novice users with dense dashboards, hidden core actions, and financial jargon — while failing basic accessibility standards like contrast, labeling, and keyboard navigation. For someone already stressed about money, the tool itself becomes another barrier.

How might we design a budgeting app that delivers scaffolded education, adjustable accessibility settings, and a simple enough experience that novice budgeters and users with disabilities can set and achieve financial goals with less stress?

Goal #1

At least 80% of first-time users create their first budget within 3 minutes

Goal #2

User satisfaction score of at least 85

Meet Edgar

Photo representing Edgar, the user research participant

Edgar is a 42-year-old HVAC manager thinking about retirement for the first time. He tried budgeting in his 20s but gave up — the tools were stressful, not helpful. As he puts it: "I've always wanted to be better with money, but it always seems too complicated, and apps that are supposed to help don't make it much easier."

Results at a glance

75% → 90%Satisfaction grew after iterative testing
A11y-first designHigh contrast, clear labels, hierarchy
Tiered complexity"Learn" hub supports financial literacy

Edgar's Goals

  • Plan for retirement effectively
  • Create simple budgets easily
  • Learn financial management basics

Edgar's Frustrations

  • Spreadsheet budgets are confusing
  • Apps hide core actions in menus
  • Visual impairment makes many apps unusable
  • Overwhelmed by financial jargon

Journey Map: Prepare for Retirement

Edgar doesn't know where to start. Here's the path from confusion to confidence.

1. Calculate Retirement Needs
Tasks
Research online; Find resources and tools; Record target amount
Feeling
Confused, Overwhelmed
Improvement
Auto-calculate using data; Plain language explanations
2. Audit Current Savings
Tasks
Log into all accounts; Calculate total assets; Track contribution methods
Feeling
Frustrated, Hopeless
Improvement
Bank integration via SSN; Auto-sum all accounts; AI contribution summary
3. Set Target & Design Budget
Tasks
Research strategies; Calculate gap amount; Define spending categories; Allocate funds strategically
Feeling
Conflicted, Determined
Improvement
AI-powered calculation; Banking app integration; AI budget suggestions
4. Create Accountability System
Tasks
Set review schedule; Choose tracking method; Plan for setbacks
Feeling
Nervous, Determined
Improvement
AI coaching suggestions; Automated reminders/alerts

Design Decisions

I scoped the MVP around the single most stressful moment for novice budgeters — creating that first budget — and built outward from there, layering in education and personalization only after the core flow tested well.

What competitors get wrong

A competitive audit of 5 budgeting platforms revealed consistent failures: unlabeled icons and charts, sub-4.5:1 contrast, fixed 12px text, no keyboard path. Tutorials hidden in help centers. Educational content paywalled or absent. Simpler apps are outgrown as confidence increases, while complex ones overwhelm novices from day one.

Ideation (Day 1)

Crazy 8s and a quick Close Up/Big Picture storyboard led me to two key decisions:

  • Give users the ability to "level-up" their in-app experience as they learn
  • Allow personalization of accessibility features early on
A pencil on paper sketch with 8 loose brainstormed ideas for the budget app layout

Testing & Iteration (Week 1–3)

Lo-fi wireframes kept every screen within two taps via a bottom tab bar. Unmoderated usability testing with 5 participants revealed my labels weren't matching user expectations. The fix: Accounts → Transactions, Planning → Budgeting, Help → FAQ. That single round of renaming raised navigation satisfaction from 70% to 90%.

Lo-fi wireframes showing onboarding flow, tab bar and sign-off flow, 2-click level switch, and transaction and budget creation screens

Interaction & UI (Week 4–6)

The initial glassmorphic style made WCAG-compliant contrast difficult, so I redesigned using iOS conventions and the 60:30:10 color rule.

Accessibility

Accessibility was a design constraint from day one — not a retrofit. Every decision below came directly from the competitive audit findings and user interviews.

Design for accessibility from day one — at least 4.5:1 contrast, built-in accessibility features, clear visual hierarchy.

Optional tutorial at onboarding, clear CTA button in FAQ page (easy access in main tab bar).

Introduce free "Learn" hub and level switching to manage information density and complexity.

Mobile-first, minimalist layout for visual and cognitive accessibility featuring clear hierarchy, fewer elements, and progressive disclosure.

Contrast Verification

Using Stark, A11y, and Able plug-ins I verified contrast across all frames. The audit revealed the brand teal on white was too low — I changed affected labels to navy to meet AA requirements.

A11y Color contrast checker plug-in on Figma confirming all texts meet AA color contrast requirements

The Work

Before & After Redesign

Before Redesign

Animated preview of the first hi-fi design with a purple glassmorphic background style

After Redesign

Animated preview of the redesigned UI with clean iOS-style layout following the 60:30:10 color rule
View Figma Prototype →

Sticker Sheet

All components grouped by category and state for fast iteration and developer handoff.

Outcomes

Five participants completed both lo-fi and hi-fi usability studies. Satisfaction rose from 75% in the first round to 90% after iterating on labels, layout, and tab navigation. All five described the app as "easy to use" and "easy to navigate."

Goal #1 Result

100% of participants (5 of 5) created a budget within 3 minutes.

Goal #2 Result

User satisfaction score = 90% (second round of usability studies)

Reflection

What I Learned

  • Build reusable components early. Compiling a design system as I worked made each round of iteration faster — a habit I'll carry into team environments.
  • The product is for the user, not the designer. Usability testing changed my labels, my layout, and my assumptions. Every round of feedback made the app better than my instincts alone would have.
  • Accessibility from day one. Centering high-contrast palettes, readable fonts, clear hierarchy, and meaningful labels from the start is easier than retrofitting — and produces better design.

Next Steps

WCAG Conformance Audit

Formal WCAG 2.2 audit — contrast, touch targets, alt text, keyboard paths, screen reader compatibility — before making any conformance claims.

Assistive Technology Testing

The usability participant pool did not include assistive technology users. Further studies with AT users are needed to validate the accessibility-first approach.

Real-World Validation

Collect task completion, retention, and goal attainment data to measure whether the app actually helps people budget — not just whether they can use it.