← All work Mobile banking · Case study

Banking that never makes you wonder where your money went.

NEXA Bank is a mobile banking app I designed end to end for a client in Türkiye, from research and information architecture to high-fidelity UI and its design system.

Role
Product designer, end to end (freelance)
Client
NEXA Bank, Türkiye
Scope
Research, UX, UI and design system for 20 core flows
Timeline
About 12 weeks of design phases
NEXA Bank screens: home, transfer, transaction notifications and transfer to bank
Core flows: home, choosing a transfer, transaction notifications and transfer to a bank. From my NEXA Bank Figma file.
Problem

A banking app asks for the most trust at the two moments people feel least sure: signing up, and sending money.

What I did

Proto-personas, user interviews, market and competitor review, an open card sort, information architecture, task flows, wireframes, UI, usability feedback and the design system.

Result

20 core flows, one primary action for every money movement, and a review step before anything is sent.

01 · Goals

Five rules for every screen

Clarity

Easy-to-follow flows for daily banking tasks.

Efficiency

Fewer steps and less time for each transaction.

Trust

Clear confirmations and secure interactions.

Consistency

Unified components and predictable behaviour.

Scalability

A structure that can take new features.

02 · Research

Who it's for, and what that changed

The audience: tech-savvy young professionals, small business owners and freelancers, and people who rely on mobile banking for daily transactions in Türkiye. I started from two proto-personas, assumption-based profiles of the people I expected to design for, then interviewed users and reviewed the market and competitors to test them, and mapped an empathy map, user journeys and problem statements. Each proto-persona below ends in the design decisions it led to.

The efficient professional

Wants to manage money fast and feel the app is secure. Frustrated by long onboarding, unclear transfer confirmations and manual logins.

So I designed: quick actions for one-tap transfers, biometric login, and an account switcher for multiple accounts.

The busy household manager

Pays bills and watches balances, finds complex apps overwhelming and worries about sending money to the wrong place.

So I designed: simpler navigation, a review screen before every transfer, and only the alerts that matter.

03 · Structure

Card sorting shaped the navigation

I ran an open card sort with users to validate the information architecture. It grouped the app into four areas, and the key outcome was simpler navigation with every kind of transfer grouped under one primary action.

Accounts

  • Balance
  • Statements
  • Linked accounts
  • Switch account

Transfers & payments

  • Bank transfer
  • Card transfer
  • QR payments
  • Bill payments
  • Transfer history

Cards

  • Debit card
  • Card settings
  • Freeze card
  • Limits

Profile & settings

  • Personal info
  • Security
  • Notifications
  • Support
  • Saved cards
Redrawn from the information architecture in my original NEXA case study.
04 · Flows

Designing the unhappy paths

Money flows fail in predictable ways. I mapped them before drawing screens, so errors have a designed answer instead of a generic alert.

Start→Select transfer type→Enter details→Review & confirm→Transfer successful
Insufficient balance → alertError → retry transfer
Redrawn from the task flow in my original NEXA case study.

The 20 core flows cover onboarding, biometric sign-in, account setup, adding a card, transfers, QR payments, notifications and card management.

NEXA transfer via bank flow: choose transfer, choose bank, details, confirmation, PIN, success, receipt
The full transfer-to-bank flow: choose the transfer, the bank and the amount, confirm, enter the PIN, then the success screen and receipt. From my NEXA design file.
05 · UI & system

A calm, minimal system for a high-trust product

From low-fidelity wireframes to high-fidelity UI, everything runs on one small system: Roboto for type, one strong primary colour for actions, and clear semantic colours for success, warning and error.

Primary #635DFF
Secondary #EEE9FF
Background #F4F4F7
Text #1A1A1A
Success #2A9D8F
Warning #EABF4B
Error #F25F5C
Border #C7C7CD
Values from the NEXA style guide.
NEXA Bank card transfer: PIN entry, transfer successful and the receipt
The end of a card transfer: PIN, confirmation and receipt. From my NEXA Bank Figma file.
06 · Reflection

What I'd push further

What is done: the research with real users (interviews and an open card sort), the information architecture, the 20 flows, the UI and the design system. What is not yet done: testing the finished flows with users at scale. The next step is validating the transfer flow: task success and time on task for a first transfer, and how often people back out at the review step.