Business Banking
on the go

A mobile app concept for Victoriabank

My role: Product Designer
Timeline: 2 months

Two phones with the VB24 Business app: the account dashboard, one above the other

38 21

navigation items

10 5

menu sections to tabs

Challenge. A business owner needs from their banking four jobs on the go, and all four live only on desktop.

Victoriabank's desktop banking with the four key business jobs spotlighted

Benchmarks. I compared the best global and local business apps to see what VB should take.

Screens from Wise, Revolut and maib: rate alerts, selling currency, payment status and accounts

How competitors handle everyday business banking: a comparison table of banking apps by task

Competitor comparison

Audit. Now the client sees a 10-section desktop menu with 38 entries: some items repeat, names shift meaning across languages, and ten document folders never signal a change.

Information architecture of the desktop platform: 10 sections, 38 entries, arrows marking repeats and ambiguous names

On mobile the platform layout falls apart: content is cut off, elements overlap, and tapping one thing triggers another.

Desktop platform in a mobile browser: content cut off and elements overlapping

Desktop platform in a mobile browser — screen 1, layout cut off

Desktop platform in a mobile browser — screen 2, overlapping elements

Desktop platform in a mobile browser — screen 3, tiny tap targets

Desktop platform in a mobile browser — screen 4, misaligned content

Hypotheses. Three things worth building, and what each one should change for the client

Three hypothesis stickies: See the money, Send a payment and Convert currency

01 · SEE THE MONEY

If we build a mobile banking app for the business owner, then they learn about incoming money as soon as possible, on the go, because the app is always in their pocket and tells them about every new payment.

Cris

02 · SEND A PAYMENT

If we make paying simple in the mobile app, then the business owner pays invoices on time, on the go, because most payments repeat, and a saved template turns one into a few taps.

Cris

03 · CONVERT CURRENCY

If we let the owner set a target rate and alert them when the bank reaches it, then they convert at the rate they were waiting for and keep more from each conversion, because the app watches the rate for them, and the alert opens the conversion right away.

Cris

Framed from an expert audit.

Not yet validated with users.

Cris

The idea I killed. Hunting the biggest client saving, I landed on the bank’s “Happy Hour.” — one hour a day at the better NBM rate, and an alert to never miss it. Then research showed the bank loses on it, so I let it go.

A sticky note: alert the owner the moment Happy Hour opens, stamped Killed

Decision. I moved 20 of 38 menu items into 5 tabs on mobile: the ones a business owner needs on the go. The other 18 stay on desktop.

Migration map: which of the 38 desktop menu items move into the 5 mobile tabs and which stay on desktop

Migration map: which of the 38 desktop menu items move into the 5 mobile tabs and which stay on desktop (untouched items dimmed)

Before

Get to a computer

Open the platform in a browser

Type the password

Confirm with mobile signature

Open the account statement

5 steps · a computer and a phone

After

Screen recording
Face ID → Home, on loop

1 step · Face ID

First launch. Login, signature, quick code, Face ID. Done once, never again.

First launch in four screens: sign in, mobile signature, quick code and Face ID

User flow. 4 actions start from Home, and the two that move money end with mobile signature.

User flow: four actions start from Home, and the two that move money end with mobile signature

User flow: four actions start from Home, and the two that move money end with a mobile signature

Wireflow: the same flows drawn with mini screens and the arrows between them

Edge cases. Every failed step tells the owner what to do next. Empty statement, statement load error - in Backlog.

Edge case — mobile signature failed, with a clear next step

Edge case — rate changed before confirmation

Before and after. The web platform hides the essentials behind a menu and drowns the exchange in noise. The app shows the important things first and nothing more.

The web platform home next to the app home

The Exchange form, typed by hand every time, next to the app conversion screen, where the rate is set by the system

Home before and after: the web platform versus the app's prioritised home screen

Currency exchange before and after: the noisy web flow versus the app's focused conversion

Alerts. The app comes to the owner: when money arrives, and when the rate reaches the target.

Lock screen with two VB24 push notifications: Money received, and the target rate reached

See the money

A push the moment money arrives. No amount on the lock screen.

Convert

A push when the bank reaches the target rate. One tap opens the conversion.

See the money

A push the moment money arrives. No amount on the lock screen.

Convert

A push when the bank reaches the target rate. One tap opens the conversion.

Tokens first. Color, type, spacing and radii all live as Figma variables.

Figma variable panels: colour, type, spacing and radii collections with their values

colors

text styles

sizes and spacings

radii

Prototype. Four jobs, one hand, no desk.

Screen recording · 1

Screen recording · 2

Screen recording · 3

Screen recording · 4

Next. The prototype is a claim. Usability testing with real clients is the proof. To validate this solution, five of the bank’s clients are required, measured on task success, time on task, error rate, and ease.

Thanks. Ask about this project, or read the next case.

Local AI for hospital meetings

Hospital boards get their minutes by email, and the audio never leaves the network.

2 days hackathon build · 2nd place

Healthtech AI Product Responsive Web

Avatar Builder

Fintech Gamification

Business Bankingon the go

Challenge. A business owner needs from their banking four jobs on the go, and all four live only on desktop.

Benchmarks. I compared the best global and local business apps to see what VB should take.

Audit. Now the client sees a 10-section desktop menu with 38 entries: some items repeat, names shift meaning across languages, and ten document folders never signal a change.

Hypotheses. Three things worth building, and what each one should change for the client

The idea I killed. Hunting the biggest client saving, I landed on the bank’s “Happy Hour.” — one hour a day at the better NBM rate, and an alert to never miss it. Then research showed the bank loses on it, so I let it go.

Decision. I moved 20 of 38 menu items into 5 tabs on mobile: the ones a business owner needs on the go. The other 18 stay on desktop.

Same bank, faster door. Everything the desktop asks for happens on the first launch only. Every next visit is Face ID or a quick code.

First launch. Login, signature, quick code, Face ID. Done once, never again.

User flow. 4 actions start from Home, and the two that move money end with mobile signature.

Edge cases. Every failed step tells the owner what to do next. Empty statement, statement load error - in Backlog.

Before and after. The web platform hides the essentials behind a menu and drowns the exchange in noise. The app shows the important things first and nothing more.

Alerts. The app comes to the owner: when money arrives, and when the rate reaches the target.

Tokens first. Color, type, spacing and radii all live as Figma variables.

Prototype. Four jobs, one hand, no desk.

Next. The prototype is a claim. Usability testing with real clients is the proof. To validate this solution, five of the bank’s clients are required, measured on task success, time on task, error rate, and ease.

Thanks. Ask about this project, or read the next case.

Business Banking
on the go