splyt

project overview

a peer-to-peer payment app designed to simplify bill-splitting among friends at restaurants.

project type

ios mobile application

year

2022

my role

co-lead

users

30,000

problem

lack of visibility and control disrupts group payments

User research—via surveys and interviews—revealed several key pain points in the legacy app:

No ability to cross-reference the original receipt, leading to uncorrected errors
Delayed payments due to users having to wait until all members were assigned
Limited moderator control over item division and visibility into selections, totals, and payment status

solution

empowering moderators and streamlining group payments

enabled moderators to check the original receipt

Allowed real-time corrections of misread or misassigned items by Splyt’s scan.

Improved receipt accuracy by 25% based on reduced moderator corrections post-launch.

2. introduced asynchronouse payments for faster checkout

Reduced friction in group payment scenarios by removing unnecessary dependencies.

Improved speed, convenience, and perceived control in the checkout experience.
Helped decrease abandonment during payment and minimized end-of-meal delays.

give moderators full visibility into group activity

reduced the need for manual follow-ups and payment confirmation outside the app.

helped reduce user drop-off and support requests related to unclear payment status

competitive analysis

No Moderator Role or Authority Model

Splitwise lacks a defined moderator or organizer role, which can lead to confusion when one person is managing the bill. Our app addresses this by giving moderators control and visibility, making group payments more organized and efficient.

user research

frustration, time pressure, and limited control: key user pain points

To understand pain points in the legacy app, the research team surveyed 75 users and conducted 6 in-depth interviews. Recurring themes included: frustration with payments and receipts, time constraints, limited control and transparency in group interactions, confusion from unclear workflows, and inconsistencies across features. These insights directly informed the problem statement and guided the design direction.

user persona: 20 years old | business major

user story:

Jordan is a busy college student juggling classes, a part-time job, and an active social life. He and his friends often go out for meals, take weekend trips, and share costs for groceries, streaming subscriptions, and Uber rides.
He’s the one who usually organizes group activities — but hates having to constantly remind friends to pay him back.

goals: