Ademola Adeagbo
Open for work Resume

Case study

Vault

A digital bank for everyday payments in Nigeria: send, pay bills, save, spend, and bet with limits.

Role
UI/UX designer (solo)
Timeline
November 2026
Platform
iOS · 390 × 844
Scope
UX, UI, design system, prototype, dev handoff
Type
Concept project
A man photographed for the Vault concept
Vault · Concept case study

451

screens in the prototype

1,940

prototype links between them

10

prototype flows

0

dead taps in the prototype

01 · Overview

One account for money in, money out and money kept

Vault is a concept for a Nigerian digital bank in the style of the apps people already use for daily payments. I designed it end to end: structure, every flow and state, a design system with interactive components, a linked prototype of 451 screens and developer handoff.

02 · Problem

Where money apps lose trust

Daily payment apps are fast when everything works. Trust breaks in the other moments: a transfer stuck on pending, a wrong account name, a failed bill payment with no token, a locked account with no clear way back. Betting top-ups also sit next to rent money with nothing to slow you down.

This is a concept project. These are my starting assumptions, to be checked in the usability tests below.

03 · Goals

Goals

01

Confirm first

Show the account or meter name before any money moves.

02

Explain failures

Every error says what happened and what to do next.

03

Stay in control

Freeze, limits, pause and devices are one tap away.

04

Fast for daily use

Send, bills and add money straight from Home.

04 · Audience

Who I designed for

A trader at a market, photographed for Vault

Traders

  • Get paid by transfer or QR
  • Need to see money land at once
  • Share receipts with customers
Friends together, photographed for Vault

Students and young workers

  • Split bills and send small amounts
  • Airtime and data every week
  • Some fund betting wallets
A woman shopping, photographed for Vault

Online shoppers

  • Pay with a virtual card
  • Want to freeze a card fast
  • Save towards a target

05 · Structure

Information architecture

Home

  • Send
  • Add money
  • Bills and betting
  • History
  • Notifications

Cards

  • Card details
  • Freeze
  • Spending limit
  • Card PIN
  • Physical card

Pay

  • Scan QR
  • My code
  • Request money

Insights

  • Monthly spend
  • Categories
  • Statement

Profile

  • Limits and tiers
  • Savings and loans
  • Security
  • Help and chat

06 · Flows

10 prototype flows, every tap linked

  1. 1Open an account
  2. 2Log in, wrong passcode, locked
  3. 3Send to a bank
  4. 4Pay bills
  5. 5Betting and limits
  6. 6Transactions and disputes
  7. 7Cards
  8. 8Home (everything)
  9. 9Offline
  10. 10Loan · not eligible

07 · Decisions

Design decisions

Name before money

Account, meter, decoder and betting IDs are checked and the name is shown before the amount step.

Errors that say what to do

“Your daily limit is ₦50,000 on Tier 1” with an Upgrade link, instead of “Transaction failed”.

Pending is its own state

Processing, pending, failed and successful each get a screen, and a pending transfer can be reported from its receipt.

Real photos

Real people paying, trading and shopping, so it feels Nigerian and everyday, not stock-template.

One bright colour

Lime marks the main action and the balance card. Everything else stays deep green, cream and white.

Hover and press built in

Buttons are a component set with default, hover, pressed, disabled and loading, so the prototype responds like an app.

08 · Betting

Betting, designed with brakes

Funding a betting wallet is one of the most common payments in Nigerian money apps. Instead of leaving it out, I designed it with controls: a daily limit, a pause that can’t be undone early, a clear block screen and support links.

  • Raising a limit waits 24 hours
  • Pause for 24 hours, 7 days or 30 days
  • Over-limit and blocked states explain why
  • Bet responsibly page with help links

09 · Design system

Deep green, lime and one typeface

  • Forest #0E2A20
  • Lime #C8F169
  • Cream #F4F6EF
  • Success #1F9D55
  • Error #C0362C

Plus Jakarta Sans

ExtraBold for balances and headings · SemiBold for buttons · Regular for reading

₦248,350.50

Balance · ExtraBold

10 · Handoff

Ready for developers

The Dev Handoff page specifies 15 screens with 39 field-level cards: element, required, input type, validation, every error message and edge cases. Components use Property=Value variants for Dev Mode, and colours and text are saved as styles.

  • 15 screens specified
  • 39 spec cards
  • Error messages written out in full
  • Buttons, chips and radios as interactive components

11 · Testing

Usability test plan

  • 8 adults in Lagos: 4 daily users of digital bank apps, 4 who mostly use a traditional bank app · 30 minutes each, think-aloud
  • Tasks: open an account, send ₦25,000 after a wrong PIN, buy electricity, report a pending transfer, set a lower betting limit, freeze a card
  • Measures: task success, time on task, errors, and a trust rating from 1 to 7

Status: planned. Results will be added after real sessions. No numbers are shown before then.

12 · Next

What I learned and what’s next

  • Designing the failure screens first (pending, wrong name, locked) shaped the happy path more than the other way round.
  • Building buttons as real components with hover and press states made the prototype behave like an app, not a slideshow.
  • Next: run the tests, then add Android, dark mode and a business account.

Prototype

Explore the prototype

All 10 flows are linked in Figma, from opening an account to a loan that isn’t eligible. 451 screens, 1,940 links, no dead taps.

https://www.figma.com/proto/lWrDfgiUsLeq1vQhb3gRGD/Vault?starting-point-node-id=33%3A29954&page-id=33%3A29111&scaling=min-zoom&content-scaling=fixed