
Building PayBridge, a pay day feature
Designed a fully self-service digital experience for customers to access short-term advances with transparent fee-based pricing across iOS, Android, and Web.
Role: UX/UI Designer → Lead Designer
Timeline: Dec 2025 – May 2026
Platform: iOS / Android / Web
Read full case studyIMPACT
~900K
Eligible accounts at launch
Customers with qualifying direct deposit history who become eligible for a PayBridge advance from day one.
55–65%
Enrollment completion rate
Projected completion for eligible customers who start the opt-in flow, from a streamlined enrollment journey.
<3 min
Time to complete an advance
Target time from opening the flow to a funded advance, thanks to optimized steps and smart defaults.

- Liquid Glass-aligned components
- Face ID-first enrollment confirmation
- Native tab bar navigation

- Material-aligned components
- Adaptive layouts for tablets
- Platform back-gesture support

- Responsive account dashboard
- Keyboard + screen-reader accessible
- Desktop-first enrollment education
Process
Discovery & requirements
Design iteration
Stakeholder review
Cross-platform handoff
Dev collaboration & launch
Discovery & requirements
Design iteration
Stakeholder review
Cross-platform handoff
Dev collaboration & launch
UX strategy
Stakeholder presentations
Created and maintained a Figma Slides deck for presenting designs to Marketing, Compliance, Fair Banking, and Legal teams.
Non-happy path documentation
Designed error states, edge cases, and alternate flows for stakeholder visibility.
Cross-platform consistency
Established shared design language and guardrails across iOS, Android, and Web.

Goal: guide users from awareness to understanding through enrollment.

Goal: users can easily take an advance that can be immediately utilized.

Goal: show how repayment works, making clear that automatic repayment is default and manual is optional.

Goal: emphasize how quick and effortless it is to opt out, with clear control and minimal friction.
Team

Ananya Nuggehalli
Lead Designer · CurrentJosh Denton
Head of ProductBailey Benton
Line of Business StakeholderPachee Yang
Technical AnalystKeaton
iOS DeveloperParker Simms
Android DeveloperZaiquise
Web DeveloperReflection
Designing while requirements moved
Discovery, design, and development happened simultaneously, so requirements evolved in real time. I leaned into a highly iterative approach with flexible component systems and close, constant communication with stakeholders — treating the roadmap as something to negotiate weekly, not lock at kickoff.
Mapping complexity into clarity
Seven eligibility rules, cooling-off periods, suspensions, and overdraft interactions meant dozens of possible account states. I mapped every state, built a clear visual hierarchy, and wrote contextual messaging that explains why an option isn't available — not just that it isn't.