Split
is a case study that explores group expense maangement
Split
is a case study that explores group expense maangement
Highlights ✨
Designed and delivered end-to-end mobile app from 0–1, covering research, user flows, wireframes, high-fidelity prototypes, and usability testing.
Conducted 6+ user interviews and synthesized findings into personas and archetypes, directly informing flows for expense creation, friend management, and receipt scanning
Built a receipt scanning flow with OCR simulation that detects restaurant metadata, itemizes bills, and assigns costs to participants, reducing manual entry by over 70%
Defined a consistent design system with scalable components, typography, and states, enabling faster iteration and a cohesive product identity
Highlights ✨
Designed and delivered end-to-end mobile app from 0–1, covering research, user flows, wireframes, high-fidelity prototypes, and usability testing.
Conducted 6+ user interviews and synthesized findings into personas and archetypes, directly informing flows for expense creation, friend management, and receipt scanning
Built a receipt scanning flow with OCR simulation that detects restaurant metadata, itemizes bills, and assigns costs to participants, reducing manual entry by over 70%
Defined a consistent design system with scalable components, typography, and states, enabling faster iteration and a cohesive product identity
Project type: End-to-end mobile app (UX research, interaction design, and high-fidelity prototype)
Role: UX/UI designer and researcher as part of a 4-person team — conducted 3 interviews, led persona development, consolidated user data, facilitated usability testing, and created the final interactive prototype
Industry: Personal Finance / Group Expense Management
Tools: Figma, FigJam, Zoom, Notion
Duration: January - March 2025
is a case study that explores group expense maangement
The goal was to minimize manual calculations, reduce social tension, and create transparency in group payments.
The goal was to minimize manual calculations, reduce social tension, and create transparency in group payments.
The goal was to minimize manual calculations, reduce social tension, and create transparency in group payments.
As the lead designer and project manager on a team of 4, I created and maintained our sprint roadmap, divided tasks across research and design phases, and facilitated weekly check-ins. With the most experience in Figma, I led the prototyping and design system work, while also supporting teammates with collaborative design tools and version control.
As the lead designer and project manager on a team of 4, I created and maintained our sprint roadmap, divided tasks across research and design phases, and facilitated weekly check-ins. With the most experience in Figma, I led the prototyping and design system work, while also supporting teammates with collaborative design tools and version control.
As the lead designer and project manager on a team of 4, I created and maintained our sprint roadmap, divided tasks across research and design phases, and facilitated weekly check-ins. With the most experience in Figma, I led the prototyping and design system work, while also supporting teammates with collaborative design tools and version control.
The Opportunity: We can ease the emotional burden of splitting expenses in social settings.
The Opportunity: We can ease the emotional burden of splitting expenses in social settings.
Through user interviews and observational research, we learned that group payments often go beyond just math, they’re wrapped in awkwardness, forgotten Venmos, and unsaid tension. The core problem wasn’t just about accuracy, but about comfort, memory, and fairness.
We discovered that the stress of splitting bills was often a byproduct of unclear communication, informal mental tracking, and unspoken social expectations.
Through user interviews and observational research, we learned that group payments often go beyond just math, they’re wrapped in awkwardness, forgotten Venmos, and unsaid tension. The core problem wasn’t just about accuracy, but about comfort, memory, and fairness.
We discovered that the stress of splitting bills was often a byproduct of unclear communication, informal mental tracking, and unspoken social expectations.
“I always mean to pay people back, but if no one brings it up, it just kind of fades into the background.”
— user interview, age 26
“I always mean to pay people back, but if no one brings it up, it just kind of fades into the background.”
— user interview, age 26
“I always mean to pay people back, but if no one brings it up, it just kind of fades into the background.”
— user interview, age 26
“We end up splitting things equally just to avoid drama, even if someone clearly ordered way more.”
— user interview, age 29
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“I hate asking my friends to Venmo me—it makes me feel petty even though I covered like $50 worth of stuff.” — user interview, age 22
“We end up splitting things equally just to avoid drama, even if someone clearly ordered way more.”
— user interview, age 29
“We end up splitting things equally just to avoid drama, even if someone clearly ordered way more.”
— user interview, age 29
I proposed using Cognitive Load Theory as a guiding framework to inform our UX decisions. Based on our initial interviews and pain point synthesis, it became clear that users were overwhelmed—not just by the task of splitting expenses, but by the mental effort required to coordinate, calculate, and communicate in group settings.
I saw strong alignment between this problem space and the theory’s emphasis on reducing extraneous mental load to support decision-making and follow-through.
I proposed using Cognitive Load Theory as a guiding framework to inform our UX decisions. Based on our initial interviews and pain point synthesis, it became clear that users were overwhelmed—not just by the task of splitting expenses, but by the mental effort required to coordinate, calculate, and communicate in group settings.
I saw strong alignment between this problem space and the theory’s emphasis on reducing extraneous mental load to support decision-making and follow-through.
= More accountability, faster payments, and less group tension
“I feel way less awkward asking friends to pay me back now.”
= More accountability, faster payments, and less group tension
“I feel way less awkward asking friends to pay me back now.”
I proposed using Cognitive Load Theory as a guiding framework to inform our UX decisions. Based on our initial interviews and pain point synthesis, it became clear that users were overwhelmed—not just by the task of splitting expenses, but by the mental effort required to coordinate, calculate, and communicate in
group settings. I saw strong alignment between this problem space and the theory’s emphasis on reducing extraneous mental load to support decision-making and follow-through.
Initial Prototype:
Creating a "Split" action
Initial Prototype:
Creating a "Split" action
To support Autonomy and Competence, we designed the request flow to feel clear and customizable. I prototyped features like editable line items, preferred payment methods, and optional reminders, giving users more control over how they split, track, and follow through on payments.
To support Autonomy and Competence, we designed the request flow to feel clear and customizable. I prototyped features like editable line items, preferred payment methods, and optional reminders, giving users more control over how they split, track, and follow through on payments.
This is one idea among many, we had 18 initial prototypes by the end of our long prototyping phase.
This is one idea among many, we had 18 initial prototypes by the end of our long prototyping phase.
Initial Prototype:
Creating a "Split" action
To support Autonomy and Competence, we designed the request flow to feel clear and customizable. I prototyped features like editable line items, preferred payment methods, and optional reminders, giving users more control over how they split, track, and follow through on payments.
This is one idea among many, we had 18 initial prototypes by the end of our long prototyping phase.
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
What I expected:
intentional, customized payment planning
I designed the request creation flow with the hope that users would take advantage of features like editable line items, receipt uploads, and smart reminders to personalize their split requests. These tools were meant to empower users to track shared expenses with more clarity and flexibility, especially in group settings.
“I’d like to split the sushi dinner, but let me adjust what each person ordered first.”
What actually happened:
set it and forget it 🫠
In testing, most users skipped customizations and simply used the default split or relied on memory. Many preferred speed over precision, which led to uneven splits and confusion later on. This revealed that we needed to reduce the effort even further and support fast but accurate behavior through nudges and templates.
“I just want to hit send and be done with it… figuring out exact costs takes too long.”
Redesign 1
We conducted usability testing and implemented best practices to overhaul the original dashboard interface. Our goal was to improve clarity, streamline user actions, and boost visual hierarchy across the app.
Adding Features
To improve and fully flush out Split's features, we developed and protopyed the following flows and features to make sure we covered differnet user needs and journeys.
Activity, Friends, and Groups Features
To improve and fully flush out Split's features, we developed and protopyed the following flows and features to make sure we covered differnet user needs and journeys.
Smart Receipt Scanning for Faster Expense Tracking
Split’s receipt scanning feature streamlines expense tracking by automatically detecting items from a scanned receipt. Users can review, correct any details, and add additional items later, reducing manual entry and saving time.
Adding Contacts & Tagging People
Split lets users easily tag and manage people for shared expenses and provides non-users a secure payback link, ensuring seamless participation.
To streamline this process, we designed multiple entry points:
Text or phone number invitations for quick, app-free payback links.
QR code scanning for instant connections and adding participants in person.
In-app contacts for users who are already using Split.
This flexibility ensures that users can easily split and track payments with both Split users and non-users, reducing friction in group transactions and improving overall usability.
Design Systems Overhaul
For Split, I created a design system focused on simplifying shared expense management by emphasizing clarity, hierarchy, and quick actions. The system integrates a soft green gradient to convey trust and balance, rounded cards for grouping key actions like New Request and Scan Receipt, and clear status indicators (e.g., Overdue, In Review, Complete) to help users instantly understand their financial activities.
I chose this color palette to evoke trust, growth, and financial clarity, with fresh mints and deep teals symbolizing stability and prosperity. Inter was selected for its clean, modern, and highly legible design, ensuring optimal readability across all screen sizes and devices.
Redesign 1
We conducted usability testing and implemented best practices to overhaul the original dashboard interface. Our goal was to improve clarity, streamline user actions, and boost visual hierarchy across the app.
Redesign 1
We conducted usability testing and implemented best practices to overhaul the original dashboard interface. Our goal was to improve clarity, streamline user actions, and boost visual hierarchy across the app.
How Do Users Account for Tip and Tax?
→ These vary by location and are significant in group dining.
→ Users may ask:
“Is tip calculated automatically?”
“Can I enter a total with tax/tip included?”
“What if everyone tips differently?”
Can Users Adjust Individual Contributions Easily?
→ If one person didn’t eat or only shared an appetizer, how is that handled?
What Happens After Hitting “Continue”?
→ Is there a review page? Confirmation?
→ Users may fear accidentally sending an incomplete or incorrect request.
Can a Request Be Saved as a Draft?
→ Especially helpful for large groups when itemizing takes time.
What’s the Default Split Method?
→ Equal by default? Manual? Based on added items?
Adding Features
To improve and fully flush out Split's features, we developed and protopyed the following flows and features to make sure we covered differnet user needs and journeys.
Activity, Friends, and Groups Features
To improve and fully flush out Split's features, we developed and protopyed the following flows and features to make sure we covered differnet user needs and journeys.
Smart Receipt Scanning for Faster Expense Tracking
Split’s receipt scanning feature streamlines expense tracking by automatically detecting items from a scanned receipt. Users can review, correct any details, and add additional items later, reducing manual entry and saving time.
Adding Contacts & Tagging People
Split lets users easily tag and manage people for shared expenses and provides non-users a secure payback link, ensuring seamless participation.
To streamline this process, we designed multiple entry points:
Text or phone number invitations for quick, app-free payback links.
QR code scanning for instant connections and adding participants in person.
In-app contacts for users who are already using Split.
This flexibility ensures that users can easily split and track payments with both Split users and non-users, reducing friction in group transactions and improving overall usability.
Design Systems Overhaul
For Split, I created a design system focused on simplifying shared expense management by emphasizing clarity, hierarchy, and quick actions. The system integrates a soft green gradient to convey trust and balance, rounded cards for grouping key actions like New Request and Scan Receipt, and clear status indicators (e.g., Overdue, In Review, Complete) to help users instantly understand their financial activities.
I chose this color palette to evoke trust, growth, and financial clarity, with fresh mints and deep teals symbolizing stability and prosperity. Inter was selected for its clean, modern, and highly legible design, ensuring optimal readability across all screen sizes and devices.
We moved forward with finalizing the remaining design elements, such as fonts, buttons, and icons, ensuring they were consistent and aligned with the selected color palette. We also developed a moodboard to define the app’s visual direction and maintain a cohesive design throughout the development process.
User Flows
After finalizing the style guides and establishing the mood and aesthetic for our project, which were crafted by another team member, I took her design choices and system and applied them directly to the user flows I created. These user journeys were informed by our earlier problem statement and user interviews, which revealed pain points around inefficient bill splitting, unclear payment requests, and difficulty managing group expenses. By mapping out key flows such as onboarding, creating a request, paying a request, and managing groups and friends, I made sure each step met user needs, reduced friction, and translated research insights into intuitive, visually consistent pathways through Split’s core features, creating a cohesive and user-friendly experience.
Feel free to check out the information architecture(IA) map I created before prototyping the following user flows below.
User Flows
After finalizing the style guides and establishing the mood and aesthetic for our project, which were crafted by another team member, I took her design choices and system and applied them directly to the user flows I created. These user journeys were informed by our earlier problem statement and user interviews, which revealed pain points around inefficient bill splitting, unclear payment requests, and difficulty managing group expenses. By mapping out key flows such as onboarding, creating a request, paying a request, and managing groups and friends, I made sure each step met user needs, reduced friction, and translated research insights into intuitive, visually consistent pathways through Split’s core features, creating a cohesive and user-friendly experience.
Feel free to check out the information architecture(IA) map I created before prototyping the following user flows below.
Redesign 2
I iterated on previous deigns after finalizing user flows, using them to validate navigation and interactions so that the updated dashboard prioritized pending and overdue balances, streamlined actions, and presented activity with clearer hierarchy and language.
Redesign 2
I iterated on previous deigns after finalizing user flows, using them to validate navigation and interactions so that the updated dashboard prioritized pending and overdue balances, streamlined actions, and presented activity with clearer hierarchy and language.
We moved forward with finalizing the remaining design elements, such as fonts, buttons, and icons, ensuring they were consistent and aligned with the selected color palette. We also developed a moodboard to define the app’s visual direction and maintain a cohesive design throughout the development process.
Split
is a case study that explores group expense maangement
Split
is a case study that explores group expense maangement
Design Systems Overhaul
For Split, I created a design system focused on simplifying shared expense management by emphasizing clarity, hierarchy, and quick actions. The system integrates a soft green gradient to convey trust and balance, rounded cards for grouping key actions like New Request and Scan Receipt, and clear status indicators (e.g., Overdue, In Review, Complete) to help users instantly understand their financial activities.
I chose this color palette to evoke trust, growth, and financial clarity, with fresh mints and deep teals symbolizing stability and prosperity. Inter was selected for its clean, modern, and highly legible design, ensuring optimal readability across all screen sizes and devices.
Components
We moved forward with finalizing the remaining design elements, such as fonts, buttons, and icons, ensuring they were consistent and aligned with the selected color palette. We also developed a moodboard to define the app’s visual direction and maintain a cohesive design throughout the development process.
User Flows
After finalizing the style guides and establishing the mood and aesthetic for our project, which were crafted by another team member, I took her design choices and system and applied them directly to the user flows I created. These user journeys were informed by our earlier problem statement and user interviews, which revealed pain points around inefficient bill splitting, unclear payment requests, and difficulty managing group expenses. By mapping out key flows such as onboarding, creating a request, paying a request, and managing groups and friends, I made sure each step met user needs, reduced friction, and translated research insights into intuitive, visually consistent pathways through Split’s core features, creating a cohesive and user-friendly experience.
Feel free to check out the information architecture(IA) map I created before prototyping the following user flows below.
