Splyt
Splyt
A peer-to-peer payment app designed to simplify bill-splitting among friends at restaurants
A peer-to-peer payment app designed to simplify bill-splitting among friends at restaurants
👥 Co Lead
👥 Co Lead
📱Mobile Application
📱Mobile Application
⏰ 1 year
⏰ 1 year
Problem
Problem
Lack of Visibility and Control Disrupts Group Payments
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
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
Solution
Empowering Moderators and Streamlining Group Payments
Empowering Moderators and Streamlining Group Payments
Empowering Moderators and Streamlining Group Payments
Enabled Moderators to Check the Original Receipt
Enabled Moderators to Check the Original Receipt
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.
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.
Introduced Asynchronous Payments for Faster Checkout
Introduced Asynchronous Payments for Faster Checkout
Introduced Asynchronous 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.
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.
Gave Moderators Full Visibility Into Group Activity
Gave Moderators Full Visibility Into Group Activity
Gave 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 statuses.
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 statuses.
Competitive Analysis
Competitive Analysis
No Moderator Role or Authority Model
No Moderator Role or Authority Model
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.
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.
Research
Research
Frustration, Time Pressure, and Limited Control: Key User Pain Points
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
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
Final Designs
Final Designs
Final Designs
