Work · Barclays · Mobile banking · iOS and Android · 2016

Effortless Transactions

Paying anyone, buying prepaid and cashing out, made quick to find and hard to get wrong.

Mobile banking for first time phone payers. I redesigned the three core jobs, tested them and rebuilt every flow in code.

25%faster to buy airtime in the beta, with fewer mistaken transfers.

The app’s name, the bank and every person are changed. Sample data.

Pay someone

Andrew Bishop

+27 72 555 0182

Amount

R500.00

Message

Dinner on Friday

From Everyday account •••• 8787

Swipe to pay
iPhone
ontheGo

Everyday account

Account •••• 8787

Available balance

R15 000.00

Current balanceR 15 399.00

Uncleared balanceR 0.00

Swipe Pay someone to the left to pay the last person again.

Android

Both phones work. Tap Pay someone to start.

The story in six lines

  1. GoalHelp a bank’s newest customers pay, top up and get cash from their phone.
  2. ProblemIn testing, nobody understood the old Cash out label, and about half tapped Add when they meant Pay., go to this part
  3. ApproachRedesign the three jobs people came for, test each one, and make the moment money leaves feel calm., go to this part
  4. DecisionA swipe to pay over a button. Engineers wanted the button; the beta settled it., go to this part
  5. LaunchTested with customers in a beta on iPhone and Android., go to this part
  6. Result25% shorter time to buy airtime, and fewer payments sent by mistake., go to this part

Select a line to read that part.

At a glance

Role
Senior UX/UI designer
Platforms
iPhone and Android
Shipped
Redesign tested in a beta
Prototype
Rebuilt in Next.js and React

Accessibility: Amounts read aloud as you type; motion stops on request.

01 · The brief

Three jobs, and every one felt anxious

People came to pay, buy airtime or get cash. Each was hard to find, and the last step gave little sign money had moved.

The brief: cut measurable friction and make large amounts feel safe.

  1. Before · 1Hard to findAfterEvery job one tap from home
  2. Before · 2An unclear balanceAfterThe balance first, and every amount checked against it
  3. Before · 3A weak last stepAfterA swipe to pay, then a clear answer: paid, or waiting

02 · Testing

What people did with the first prototype

People rarely read; they judged by what stood out. Every finding changed a screen.

Who we tested with

  • A mix of men and women, aged 19 to 24
  • Students and people in their first jobs
  • Everyday smartphone users, all on Android by chance
  • Few had used a payment app; most paid a friend back by covering the next round
“If everything could be on my phone, that’d be great.”
A participant, on paying by cellphone number

Most were wary of paying by phone number, until they realized they had every friend’s number.

  1. 01 · Swipe to pay

    Most swiped up first, or tapped.

    So the swipe is used for nothing else, so it always means money moves.

  2. 02 · After paying

    Nearly everyone asked what happens next.

    So the last screen says plainly where the money is.

  3. 03 · Cash out

    Nobody understood the old label.

    So it’s called Cash out, explained in three steps.

  4. 04 · Choosing a contact

    Half tapped Add when they meant to pay.

    So search sits on top; adding is a small icon.

  5. 05 · Warnings

    Confirmations went unread.

    So warnings sit under the amount, in color, as you type.

  6. 06 · The menu

    Nobody understood Device management.

    So the menu uses plain words only.

  7. 07 · Buy prepaid

    The easiest task of all.

    So bundles stay up front.

  8. 08 · Who it’s for

    People struggled to find their own name.

    So prepaid opens with For me first.

Decisions behind it

Three calls that shaped it

  1. The call I made

    A swipe to pay, not a button

    A swipe costs a second more than a tap. That second stopped accidental payments in the beta.

  2. What I dropped

    A home screen of every service

    People came for three jobs, so home became pay, prepaid and cash out.

  3. The constraint

    A payment that stalls

    The number is checked first, and a stalled payment always says where the money is.

03 · The flows

Every step, and every way off it

Each job mapped from start to finish, with every way it could go wrong. These were the developer handoff.

Drag to move around. Zoom with the buttons, a pinch, or Ctrl and scroll.

From home to paid, for someone new, and every way off it.

100%

Redrawn from the project’s flow diagrams with this prototype’s screens. Every phone on the map is the working app, held at that step.

04 · Swipe to pay

A gesture you can’t make by accident

A swipe, not a tap: a moment of intent that always means money moves.

Cancel is always one tap away.

With a keyboard, focus the circle and press Enter.

Pay someone

Noni Bandela

+27 72 555 0172

Amount

R250.00

Message

Concert tickets

From Everyday account •••• 8787

Swipe to pay
Live: drag the circle to the end of the bar.

05 · The balance

You never get as far as paying what you don’t have

Every amount is checked against the balance as you type.

Pay someone

Sam Randall

+27 72 555 0155

R16 353

Live: delete a digit or two and Continue comes back.

06 · Someone new

One extra check, only when it counts

A first payment to someone new needs a yes on your phone.

Someone not on the app gets a text; the money waits 48 hours, then returns.

  1. Step 1Swipe to paySomeone you’ve paid before, already on the app: paid at once.
  2. New recipientApprove on your phone25 seconds to answer. Missed it? Send it again, or use a one time code with three tries.Not on the app yetThey get a text to joinThe money waits 48 hours, then comes back to you on its own.
  3. ThenPaid, or waiting for them to joinEither way it shows in Transactions, with what happens next.

07 · The rest of the app

Prepaid, cash out and everything the original never had

I designed the rest on the same rules: data, electricity, cash out with a code, sign in and settings.

Cash out

How much cash do you need?

You’ll get a code to use at any partner ATM. No card needed.

Available balance is R 15 000.00

Live: choose an amount and a PIN to get a cash code.

08 · Details

Plain words when it goes wrong, and at home on both phones

Each problem gets one plain sentence where it happened. Red stops you; orange needs a look.

The brand holds; everything else follows the platform.

  • Too much

    More than your available balance of R 15 000.00

  • Note too long

    3 too many

  • Wrong code

    That code isn’t right. 2 tries left.

  • No answer in time

    The request timed out. Send it again and approve it when it arrives.

  • They didn’t join

    Thato didn’t join in time, so the money came back to you.

  • No matches

    No contacts match “Anupr”. Check the spelling, or add them as a new contact.

  • Over the limit

    Airtime can’t be more than R 1 000 at a time

  • Nothing yet

    Nothing is waiting. Payments to people who aren’t on ontheGo show here until they join.

How the app follows each platform
PartiPhoneAndroid
TypeSan Francisco, the system fontRoboto
TitlesCentered, shortBeside the back arrow, larger
TabsA segmented controlUnderlined tabs
MenuYour picture, then a grouped listA drawer from the left
AlertsCentered alert, side by side buttonsDialog with text buttons on the right
Sign inFace IDFingerprint
Going backThe chevron at the topAlso the system back button
Moving between screensSlides in from the rightRises and fades in

09 · Impact

What changed after the redesign

faster to buy airtime, in the beta
~25%faster to buy airtime, in the beta
mistaken transfers in the beta, once paying became a swipe
Fewermistaken transfers in the beta, once paying became a swipe
positive on navigation, compared with other banking apps
~80%positive on navigation, compared with other banking apps

Try it on the phone you know.

Pay someone new and approve it, buy airtime for a friend, or get a cash code. Every screen works, on iPhone and on Android.