Davit Arakelyan
← All work
Case study · Self-initiated concept · 2026

FastBank.

Money, made simple. A concept for a mobile bank that makes everyday money jobs feel simple: check a balance, pay a friend, share an account, save for a goal.

FastBank concept: the Home screen in the middle, with card customisation and send-as-chat screens either side
Fig. 01FastBank, a concept mobile bank. Home in the middle, with card customisation and send-as-chat either side.
Role
Product design · UI design · Design system
Platform
iOS app · 390 × 844 screens
Year
2026
Scope
7 core flows · dark & light themes
01Overview

Everyday banking, with nothing in the way.

FastBank is a self-initiated concept for a mobile bank built around the things people do every day: check a balance, pay a friend, put money aside. I designed seven core flows and the design system behind them, in a dark and a light theme.

Not a real bank. Every name, merchant and amount is fictional.

Project at a glance: project, role, scope and tools, three design intents and phone screens of the seven flows
Fig. 02Project at a glance: role, scope, three design intents and the seven flows.
02Problem

Banking apps can make simple jobs feel heavy.

Most money tasks are small. You check what’s left, pay someone back, put a little aside. But many banking apps make you hunt for them: menus inside menus, fees you find out about afterwards, shared spending you can’t follow, and savings screens full of numbers you aren’t sure you can trust.

I wanted to see how calm a bank could feel if every screen did one job well. The brief I set myself:

  1. Put the number that matters first on every money screen.
  2. Show fees and arrival times before you commit, not after.
  3. Make shared money clear about who paid.
  4. Talk about savings and interest honestly, with no promised rates.
  5. Build it all on one set of tokens, so dark and light come from the same source.
Five numbered rule cards that every FastBank screen is checked against
Fig. 03The five rules every FastBank screen is checked against.
03Users & research

Starting from the jobs, not the features.

This is a concept, so I didn’t run interviews or user tests for it. I started with desk research: I reviewed common mobile-banking patterns, the jobs people most often open a banking app for, and published accessibility guidance. From that I wrote down the assumptions the design has to prove.

Who I designed for: two proto-personas, built from assumptions rather than interviews. Lilit, the everyday organiser, shares a joint account with her partner and saves for a house deposit. Mira, the friend who splits the bill, pays and gets paid back in small amounts, usually right after a chat about dinner plans.

Research board: five assumption cards, proto-persona cards for Lilit and Mira, and a Next: validate panel
Fig. 04Five assumptions from desk research, each shaping at least one screen, two fictional proto-personas, and how I’d validate them next: moderated usability sessions, a first-click test on Home and an accessibility pass. Proposed, not yet run.
04Flows

Seven flows, each with one clear goal.

Before drawing screens I mapped each flow as a short path, from where it starts to the moment you know it worked. The goal was fewer steps and no dead ends. Every money flow ends on a clear confirmation.

Flow diagram with one row per flow
Fig. 05Seven flows mapped from start to confirmation. Each money flow shows cost and outcome before the last tap.
05Key screens

Seven core screens, in dark and light.

Each screen does one job. The number that matters comes first, and cost and timing show before you commit.

Sign-in: welcome back, in one step.

Returning users land on a passcode screen that keeps the brand quiet and the task obvious: six dots, a large keypad, and biometric unlock offered in context, with the passcode always there as a fallback.

Sign-in screen with passcode dots, biometric unlock card and a large keypad
Fig. 06Sign-in. One task on screen, biometrics offered, passcode always there.

Home: your balance first.

Home leads with the balance of the selected account. Neighbouring accounts peek in from the edges, four round actions handle the everyday jobs, and recent activity and automations sit in cards below.

Home screen showing €2,840.00 in the Personal account
Fig. 07Home. Good afternoon, Lilit: €2,840.00 in Personal, with Joint and Travel peeking in from the sides.

Card customisation: see it as you go.

The card preview is the hero. Three tools sit under it (Generate, Sticker and Text) with colour, finish and type as simple choices below. The preview updates as you change them, and ordering is one button away.

Card customisation screen with a live card preview
Fig. 08Card customisation. Colour, finish and name change the preview live, then one tap to order.

Transfer: the amount is the screen.

Paying a contact shows who it’s going to, a large amount, and the fee and arrival time in plain words before you continue. The source account is a pill you can change without leaving the screen.

Transfer screen sending €45.00 to Mira
Fig. 09Transfer. €45.00 to Mira, no fee, usually arrives in seconds. All of it visible before you continue.
Four numbered phone screens of the transfer flow
Fig. 10From “Pay someone” to “Sent” in four screens: pick Mira, type €45.00, check the fee and arrival time, confirm, and land on a clear “Sent”.

Joint account: clear about who paid.

On the joint account, every row names the person behind the spend, filters split activity by Lilit or Arman, and the upcoming rent share is pinned at the top so it never arrives as a surprise.

Joint account transactions with person filters
Fig. 11Joint account. Every spend names who paid, and the rent share is flagged two days ahead.

Savings pot: progress you can see.

The House deposit pot shows the balance against its goal, a progress bar and this month’s numbers. Interest is always described as an estimate on a variable rate, and no real rate is shown in this concept.

House deposit savings pot with three callouts
Fig. 12House deposit pot. €5,240 of €25,000 (21% of goal), interest shown as an estimate on a variable rate, and this month’s saved and earned amounts.

Send as chat: paying a friend, inside the conversation.

Money and messages share one thread with Mira. Requests and payments are cards with a status tag and a large amount, clearly different from text, and Request and Send sit right above the message box.

Chat thread with Mira where a €32.50 dinner request is paid
Fig. 13Send as chat. Mira requests €32.50 for dinner, you pay it in the same thread.

Dark & light: same app, two moods.

Dark is the default: deep navy surfaces that let the balance and the magenta accents stand out. Light mode is the same layouts with the theme switched in the token file. Nothing is redrawn. Every text and colour pair was checked for comfortable contrast in both themes.

All seven screens in dark and light themes
Fig. 14All seven screens, dark on top, light below. One set of layouts, one token file, contrast checked in both themes.
06Design system

Built from a few parts, used everywhere.

Every screen is assembled from the same small set of tokens and components, rendered in both themes with their interaction states.

Brand: a full stop that says “done”.

The identity is deliberately small: one typeface, two brand colours and a magenta dot. The dot works like a full stop after the name, the same idea as the tagline “Money, made simple.”

FastBank brand board
Fig. 15Brand. Inter wordmark, a navy app icon with a capital F, and the magenta dot that ties it to the tagline.

Components and tokens.

Design system board
Fig. 16Design system. Spacing, radii, surfaces, buttons, chips and action orbs, each shown in both themes with its states.

Motion (proposed): movement that confirms, never distracts.

Motion in FastBank has one job: show that something happened. It’s short, it eases out, and it respects the system’s reduced-motion setting. Proposed timing, a design spec rather than a measurement: small changes about 150–200 ms, screen transitions about 250–300 ms, ease-out. With reduced motion on, everything becomes a simple fade.

Four proposed motion moments
Fig. 17Four proposed motion moments: the balance settles in, the card responds, “Sent” feels finished, bubbles arrive in order. Proposed timing and the reduced-motion fade, a design spec rather than a measurement.
07Outcome & next steps

What I set out to do, and what comes next.

FastBank is a concept, so there are no live users or numbers to report. Here’s what the project delivers, the goals it was designed against, and what I’d do next.

Delivered

  • Seven core flows, each in dark and light.
  • A brand, a token file and a component set that build every screen.
  • Copy for every screen, including errors and empty states.

Design goalsTo be tested

  • Read your balance in a single glance.
  • Know the fee and arrival time before you send.
  • See who paid on a shared account without opening a row.
  • Track a savings goal without wondering what the numbers mean.

Next steps

  • Run usability sessions on the transfer, send-as-chat and joint-account flows.
  • Run a first-click test on Home and an accessibility pass with screen reader and large text.
  • Build the new-account onboarding and the full transfer prototype.
Outcome board and closing band
Fig. 18What was delivered, the design goals still to be tested, and the next steps, then the closing band: “If FastBank made money feel a little simpler, that’s the point.”
Next project

Aurelume Live Casino

Live casino brand concept

View case study →
Aurelume Live Casino cover
Contact

Let’s get in touch.

Open to remote roles. Let’s talk.

davitarakelyan92@gmail.com