Project Overview
I rethink the expense splitting feature of Google Pay to reduce difficulties in managing group expenses. This self-initiated case study addressed a significant issue: users were spending more time on each split due to hidden features, group setups and repetitive tasks. By conducting user research, analyzing competitors, and creating empathy maps, I identified key problems such as low discoverability (Play Store reviews overlooking the feature) and inflexible payee management. My solution implemented a transaction-based split process, quick one-time splits, and context-sensitive suggestions, simplifying a multiple step into just fever clicks. This user-focused approach, validated through wireframes and prototypes, transformed the experience of splitting payments from a tedious task into a smooth social interaction.
“Google Pay is a secure mobile payment and digital wallet platform developed by Google. It allows users to link their credit or debit cards to make online and in-store payments, peer-to-peer transactions, and money transfers. It supports contactless payments, loyalty programs, and integrates seamlessly with various apps and services…”
About the app
What is the problem?
The existing payment-splitting process has several issues, including difficulty in finding features, the need to create unnecessary permanent groups for one-time splits, and the repetitive selection of the same participants. Users also face challenges due to the absence of transaction context and a fixed procedure for adding new recipients, which complicates the process and makes it cumbersome and ineffective.
Pain Points
Poor Feature Discoverability
The split option is buried deep within menus, making it hard for users to find without prior knowledge or excessive effort.
Unnecessary Group Creation
Users are forced to create permanent groups even for one-time splits, adding clutter and extra steps to a simple task.
Repetitive User Input
The system doesn’t remember frequent payees or past groups, forcing users to reselect the same members every time.
Lack of Transaction Context
Users can't see the original transaction amount during the split flow, leading to confusion and potential errors.
Disruptive Workflow for Adding Members
Adding a new recipient mid-process breaks the flow, requiring users to exit, update contacts, and restart the task.
Empathy mapping
Affinity mapping
Feature ideations
Design Solutions ( Features Suggestions ):
Other projects
