SCB Easy (Re-Design)

A self-initiated redesign of a Thai mobile banking app, focused on making everyday money tasks faster, clearer, and less stressful for both first-time and power users.

SCB Easy redesign home screen on iPhone

This is a self-initiated concept project created for portfolio purposes. It is not affiliated with, endorsed by, or commissioned by Siam Commercial Bank (SCB). All research and design decisions are my own.

Process

  1. Discovery
  2. Ideation
  3. Design
  4. Usability Testing
  5. Handoff

Overview

This project explores how a clearer information architecture, a task-first home screen and stronger trust cues can reduce errors and build confidence in every transaction.

Tools

FigmaMiroClaude

Discovery

Goal

Understand what everyday users are trying to get done and where they get stuck, so the redesign solves real friction rather than just refreshing the visuals.

Research Process

To speed up desk research, I used Claude Code as an AI research assistant to gather information on competitor mobile banking apps and run an initial business analysis. I then reviewed and validated the findings myself before turning them into design insights.

User Interview

Pain Point

  1. Crowded home screen: Users scroll past promotions and rarely used services to reach the 2–3 tasks they do daily (transfer, scan QR, check balance).
  2. Low-visibility Scan to Pay : The Scan button does not stand out, so users rely on muscle memory to find it rather than spotting it at a glance.
  3. Inconsistent Iconography : Icons are small, hard to recognise, and inconsistent in style.

User Interview

Gain

  1. Refreshed, Focused Interface : A refreshed UI with bolder strokes, larger icons and stronger widget colours that guide the user’s eye to key actions.
  2. More Visible Scan to Pay : The Scan button stays in its original position to respect existing muscle memory, but now uses a white style for higher contrast. A second Scan to Pay entry point was also added to the navigation bar.
  3. Clearer Iconography : Icons use thicker strokes and surface-colour backgrounds, making them easier to recognise and more eye-catching.
คุณเก้น persona photo

คุณเก้น

Age: 29
Position : Youtuber

Bio

ผู้ใช้งานแอป SCB เป็นประจำที่ใช้ฝาก โอน จ่ายเงิน ในชีวิตประจำวันอยู่แล้ว

Goal
  • รู้สึกว่าสีปุ่มการโอนมองยาก ถ้าเทียบกับแอปธนาคารอื่น
  • ที่เคยใช้มารู้สึกมองยากสุดแล้ว และแอปดีไซน์ดูเก่า จัดหมวดหมู่ไม่ค่อยรู้เรื่อง อยากให้ดูคลีนสบายตาขึ้น
คุณจ๋าย persona photo

คุณจ๋าย

Age: 37
Position : Full stack developer

Bio

เป็น HR ของ สำนักงาน กกพ. ที่ดูแลพนักงานของ สำนักงาน กกพ.

Goal
  • อยากให้แอปพลิเคชัน ปรับปรุง UI ใหม่หน่อยเพราะรู้สึกมันเก่าไป
  • แต่เริ่มชินกับฟังชันก์เดิมแล้ว แต่ถ้าปรับให้ใช้ง่ายขึ้นก็โอเคร
Open app
Find transfer
Enter details
Confirm
After transfer
Action
Logs in with PIN / Face ID
Scrolls home to find the button
on process payment number or enters amount
Reviews and taps confirm
Saves or shares slip
Feeling
😐 Neutral
📋 Familiar
🔍 Focused
Neutral or Annoyed
Relieved
Opportunity
Faster login
Task-first page
Scan pay and Statement
Faster QR and Scan
-

← Swipe to see the full journey →

Problem statements

1create a clear focal point on the home screen, so users know where to look first?
2help users find Scan to Pay instantly, without breaking their existing muscle memory?
3make icons easier to recognise at a glance?

Requirements Analysis

Before designing any screens, I used Claude as an AI assistant to support the requirements analysis. It helped me structure the requirements faster and compare options when making key decisions, while I reviewed every output and made the final calls myself.

Business goals

Business goalUser goalSuccess metric
Increase daily digital transactionsPay and transfer in secondsTime to complete a transfer, taps per task
Reduce wrong-account transfers and fraud lossFeel certain before confirmingTransfer cancellation at review step, wrong-recipient
Increase engagement beyond transfersSee where money goesWeekly visits to Insights

Ideation

With clear problem statements, I restructured the app around user goals instead of bank products, then mapped the key flows before moving into wireframes.

Information Architecture

I created the Information Architecture and Sitemap to understand the overall journey of the system before moving into the design phase.

SCB App (new IA)

Home

  • Balance
  • Quick actions (customisable)
  • Recent activity
  • Alerts

Pay & Transfer

  • Transfer
  • PromptPay
  • Scan QR
  • Bill payment
  • Top-up
  • Scheduled payments

Insights

  • Monthly spending by category
  • Budgets
  • Statements

Profile

  • Cards
  • Security
  • Limits
  • Notifications
  • Settings
  • Help

User Flow

ActionScreenDecision (labelled with its business rule)End state

Process 1: Login & Homepage

User flow – Process 1: Login & Homepage

Process 2: Transfer money

User flow – Process 2: Transfer money

Use case Diagram

Use case diagram of the SCB mobile banking concept

Wireframes

Claude Design supported me during the low-fidelity stage, helping me turn my sitemap, requirements and use cases into wireframes in a fraction of the usual time. This let me spend less time on layout drafting and more time reviewing the flow, refining each screen and moving into high-fidelity design.

Option A – Card stack wireframe
Option B – Task-first wireframe (chosen)
Option C – Feed wireframe

Design

I built the visual foundation on SCB’s signature purple, extracting the core brand colours directly from the official website to keep the concept recognisable and on-brand.

Design system

Design system: typography, colors, spacing and components
Banking components: input field, status banner, recipient card, transaction list, bottom navigation

Usability Testing

Tasks

To validate the redesign, I ran a usability test in which participants completed a series of real-life banking scenarios, such as making a transfer and scanning a QR code to pay. I observed where they hesitated or made mistakes, and measured how easily they completed each task. The key results were as follows:

MenuScenarioSummary
Homepage"It's payday today. You want to know whether your salary has arrived and what your latest transaction is."Sees the balance and latest transactions
TransferYou need to transfer 300 baht for your share of a Sushiro meal you splitCan transfer straight from the home-screen shortcut, though some still follow the app's old journey
Scan to payPay for a coffee by scanning the shop's QR codeCorrect first click (original Scan button or nav bar) within 3 seconds
Screen TestShow the Home screen for 5 seconds, then ask: "What did you focus on first?"Identifies the Scan button and the account balance summary
Icon testShow icons one at a time without labels, then ask: "What do you think this icon is?"Answers all correctly; less-used icons may take a moment of thought

Design Iteration & Refinement

After usability testing, I refined the design based on the areas users most wanted improved. I updated the visual style to feel more contemporary, made the payment button stand out as the primary action on the home screen, and added a quick balance view so users can check how much money they have at a glance, without extra taps.

Before
SCB Easy home screen – before redesign
After
SCB Easy home screen – after redesign

Final Interface

The final high-fidelity screens for the core banking journeys

SCB Easy redesign – Scan Face ID screen
Scan Face ID
SCB Easy redesign – Homepage screen
Homepage
SCB Easy redesign – Accounts screen
Accounts
SCB Easy redesign – Profile Menu screen
Profile Menu
SCB Easy redesign – Setting screen
Setting
SCB Easy redesign – Account Detail screen
Account Detail

Develop Handoff

To bridge design and development, I used Claude Code to turn my Figma designs into a high-fidelity coded demo. Because the demo runs like a real app, it also served as the prototype for usability testing, giving participants a more realistic experience than a clickable mockup. Since it was built on the same design tokens imported into Figma, the demo also shows developers exactly how components, states and interactions should behave in code.