Split. Settle. Done
SplitEase | Seamless expense sharing for groups
COMPANY
SplitEase
ROLE
Product Designer
EXPERTISE
UI/UX Design | Interaction Design | Mobile App Design
YEAR
2026
Planning
A focused one-to-five week sprint from research to high fidelity design.
Built from a real frustration
SplitEase is a mobile payment splitting app designed to help groups of friends manage shared expenses fairly and transparently. Whether it's a dinner, a trip, or a night out. SplitEase makes sure everyone knows what they owe and nobody has to be the awkward one asking to be paid back.
This project was designed as part of a product design recruitment process, with the goal of solving a problem that's as social as it is financial. I designed 18 screens, a user flow, a style guide, and a full component library all in Figma.
PROBLEM
Group outings dinners, trips, events are a normal part of social life. But splitting costs fairly is anything but simple. One person ends up fronting the bill, then comes the awkward follow-up: who paid for what, how much does each person owe, and how do you actually collect without ruining the vibe?
Existing solutions either require too much manual input, feel overly transactional, or simply don't fit the Nigerian social context where cash and informal payments are common. As someone who's lived this exact frustration, I set out to design something that feels natural not like accounting software.
Meet the people SplitEase is for?
Understanding the real pain behind the split
Research was informed by personal experience and assumption based analysis of common group payment scenarios particularly within Nigerian social contexts where informal, cash based payments are still prevalent.
Designed to remove friction, not add it
Every design decision was made with one principle in mind: the app should handle the uncomfortable parts of group payments so users don't have to.
Mapping the core journey
The primary flow focuses on the most critical action: adding a bill and splitting it with a group. Every branching point was designed to reduce cognitive load and get users to completion in as few steps as possible.
Key flows covered: Onboarding → Create Group → Add Bill → Choose Split Type (Equal / By Item / Custom) → Confirm → Send Requests → Track Payment Status → Receive Reminders.
Structure before style
Wireframes were used to lock in the information architecture and interaction patterns before introducing any visual design. This made the hi-fi stage faster and more intentional.
Colors & Typography
Inter - sole typeface throughout. Hierarchy is created through weight and size, not mixed fonts.
FINAL DESIGN
The finished 18 screens
High-fidelity screens built on a consistent design system dark navy backgrounds, a green primary palette, and a clean layout system using inter and the defined 4px grid.
REFLECTION
What I learned building this
DESIGNING FOR EMOTION
Money is a sensitive topic, especially between friends. Every micro copy decision, from reminder text to button labels had to feel warm and non-confrontational. This pushed me to think beyond UI patterns into tone and voice.
SPEED VS. DEPTH
Designing 18 screens under a deadline taught me how to make fast, intentional decisions without second guessing every detail. A defined design system early in the process was the biggest time saver.
THE VALUE OF A COMPONENT LIBRARY
Building reusable components from the start meant the high-fidelity phase moved quickly and stayed consistent. I'd never skip this step again even under a tight deadline.
IF I HAD MORE TIME
I would have conducted real user interviews to validate my assumptions, tested the split flow with actual users, and explored edge cases like partial payments and disputed bills more thoroughly.
