Keep the actions in reach
Transfer and send sit above the detailed account view.
Back to workBE FREE / Banking and benefits
Saving is familiar.
Pooling isn’t.
A new way to save needed a familiar place to start. I designed the mobile and desktop UI for a banking product built around shared savings and tiered rewards.
Explore the interface
- My role
- UI designer
- Platforms
- Mobile and desktop
- Core challenge
- Make benefits pooling clear
- Foundation
- One shared design system
The design challenge
New concept.
Familiar footing.
The product connects pooled savings with benefits such as cellular data and phone perks. My job was to make that idea readable alongside everyday banking.
The promise
Save together, progress through tiers, and unlock benefits.
The interface responsibility
Keep balances and everyday actions clear while showing how pooling fits into the account.
Put savings together
Pooling gives shared savings a distinct place in the product.
See the next tier
Progress connects the current position to the next benefit.
Understand the reward
Concrete perks give the savings concept something recognizable.
Mobile / One question at a time
Money has enough questions.
The screen shouldn’t add more.
Explore four parts of the interface and the job each one does.
My balances
Start with what’s mine.
Account names and balances lead the overview. Pooling appears within the same account structure as everyday savings.
- The design choice
- Repeat the account-card pattern so a new account type has a familiar place.
- The question to validate
- Can someone distinguish their everyday accounts from their pooling account?
Desktop / More room, same priorities
A wider view.
Not a stretched phone.
Accounts, activity, and transactions share the desktop view. The challenge changes from stacking information to helping someone compare it.
Give each column a job
Accounts, activity, and transactions are grouped for comparison.
Keep benefits in context
The next reward sits alongside account activity.
Across both platforms
Consistency you
don’t have to think about.
Shared dimensions, spacing tokens, grids, and icon guidance kept mobile and desktop connected. The layout changes; the product’s visual language stays recognizable.
01
Space
Common spacing and size decisions.
02
Structure
Grids adapted to the screen.
03
Details
Consistent icon guidance.
The contribution
One concept.
Two connected experiences.
I designed the mobile UI and desktop dashboard around a shared system, bringing the pooling concept into familiar banking patterns.
Confidential project. Existing portfolio visuals are shared with permission; some are representative and details are simplified.
What I’d do differently
Test the unfamiliar part first.
I’d test pooling earlier: what people think it means, where they expect to find it, and what they understand about the tiers.
Make handoff less of a relay race.
I’d simplify the review and approval loop so decisions reach implementation with fewer passes.
What these screens don’t prove
They show interface craft and cross-platform consistency. They do not establish user comprehension, launch performance, or a measured change in conversion.
Have a complex idea
that needs a clear interface?
Let’s talk 