SplitSavvy

Reduced confusion and input fatigue by rethinking how users track and split expenses

Sentence-based UI for transaction splitting

OVERVIEW

Designed a sentence-based budgeting concept that helped users split shared expenses more clearly, reducing friction and improving collaboration.

BACKSTORY

Started From a Personal Pain Point

I couldn’t find a budgeting app that made splitting expenses feel intuitive. Most tools focused on solo finances, not shared ones. This inspired me to rethink how groups could manage spending together, without spreadsheets.

OPPORTUNITY & INSIGHTS

Apps Ignored Shared Spending and Have Trust Concerns

With limited time, I analyzed top budgeting apps instead of interviewing users. Key takeaways:

No easy way to split by user, category, or merchant
Tables were the default UI, but felt cold and rigid
Many users feared linking their bank due to privacy concerns

These gaps revealed an opportunity to design a lighter, more user-friendly way to track shared money.

With limited time, I analyzed top budgeting apps instead of interviewing users. Key takeaways:

No easy way to split by user, category, or merchant
Tables were the default UI, but felt cold and rigid
Many users feared linking their bank due to privacy concerns

These gaps revealed an opportunity to design a lighter, more user-friendly way to track shared money.

With limited time, I analyzed top budgeting apps instead of interviewing users. Key takeaways:

No easy way to split by user, category, or merchant
Tables were the default UI, but felt cold and rigid
Many users feared linking their bank due to privacy concerns

These gaps revealed an opportunity to design a lighter, more user-friendly way to track shared money.

CHALLENGE

Make it Feel Personal, Not Transactional

Most splitting tools felt like math homework. I needed to simplify complex inputs while keeping users engaged. I storyboarded flows and tested formats until I landed on a more guided, sentence-style input.

SUCCESS METRICS

Mixed Reactions, but Clear Usability Insights

Tested with 5 users. Feedback was direct and shaped the next steps:

80% preferred seeing exact dates like "Sep 5" over vague labels like "Yesterday"
60% were confused by repeated “Enter” buttons and unclear states

Tested with 5 users. Feedback was direct and shaped the next steps:

80% preferred seeing exact dates like "Sep 5" over vague labels like "Yesterday"
60% were confused by repeated “Enter” buttons and unclear states

Tested with 5 users. Feedback was direct and shaped the next steps:

80% preferred seeing exact dates like "Sep 5" over vague labels like "Yesterday"
60% were confused by repeated “Enter” buttons and unclear states

Reduced steps after users reported flow interruptions

Users didn’t understand or notice “Enter”

KEY DECISIONS

Turning Spreadsheets Into Guided Input

I started with familiar table layouts, but they felt stiff. I pivoted to a sentence-builder that broke the process into smaller, readable steps.

Each part of the sentence was editable, helping users focus on one piece at a time.

I started with familiar table layouts, but they felt stiff. I pivoted to a sentence-builder that broke the process into smaller, readable steps.

Each part of the sentence was editable, helping users focus on one piece at a time.

I started with familiar table layouts, but they felt stiff. I pivoted to a sentence-builder that broke the process into smaller, readable steps.

Each part of the sentence was editable, helping users focus on one piece at a time.

Before: Tabular Format

After: Sentence-based Format

Mapped journey to refine screen-to-screen logic

The Prototype Missed, But the Format Had Promise

Most users didn’t find the prototype useful, but I saw promise in the format. I treated the feedback as signals for refinement, not rejection.

Initial Loading Screen

Entering a Transaction

Splitting a Transaction

LEARNINGS

Research Early, Even in Fast Sprints

Without real user input, I designed based on assumptions. Even one or two quick interviews would’ve saved time.

Words Matter as Much as Layout

Button copy like “Enter” caused hesitation. UI text is part of usability and needs testing like any other element.

Validate Pain Points Before Solving Them

Not every user shared my problem. Next time, I’ll test the need first before jumping into solutions.

SEE MORE OF MY WORK

VidSeo Pro

Spotify Unite

Ghost Mode

SEE MORE OF MY WORK

VidSeo Pro

Spotify Unite

Ghost Mode

SEE MORE OF MY WORK

VidSeo Pro

Spotify Unite

Ghost Mode

GET IN TOUCH ✧ LET'S TALK ✧

GET IN TOUCH ✧ LET'S TALK ✧

Instagram

sulitdexter@gmail.com