DUOLABS
Work

Mobile banking app development

We joined the mobile team of a major Korean bank's personal mobile banking app as a developer. We built and fixed features tied to banking screens such as account lookup, transfers, financial products, and utility bill payment. In a banking app, one wrong input value or one wrong button state blocks the user's task, and the more users there are, the further a small change reaches. In a large project where several vendors, planners, PMs, and server, web, and mobile developers moved together, we kept our scope clearly defined.

Launch
2017
Client
A major Korean bank
Type
Banking & Identity
01 / 04

Banking features that run from account lookup to utility bill payment

A major bank's personal mobile banking app lets customers handle account lookup, transfers, financial products such as deposits, savings and loans, and utility bill payment on their smartphone, with funds, foreign exchange, and card services in the same app. As a developer on the mobile team, we built features connected to those banking screens. Because many teams split the app between them, we worked by checking where our features met other teams' screens.

Banking features that run from account lookup to utility bill payment
02 / 04

Stabilisation that checked input values, button states, and error messages screen by screen

In a banking app, input values, button states, screen transitions, and error messages directly affect whether users can get their task done. We checked the behaviour and exception cases of the mobile banking app's screens one by one. For each screen, we settled what state a button should be in when input is wrong and what message should tell the user.

Stabilisation that checked input values, button states, and error messages screen by screen
03 / 04

Fixes in live service that kept existing banking flows intact

The mobile banking app was already in use by a great many people, so any fix had to leave existing banking flows as they were. We made the necessary fixes and improvements while keeping those flows intact. This work made it concrete that in a service with many users, even a small change goes in only after thorough verification.

Fixes in live service that kept existing banking flows intact
04 / 04

Scope coordination in a large project where planning, PM, server, web, and mobile moved together

Developing the major bank's mobile banking app was a large project in which several vendors and stakeholders moved together. Requirement changes, acceptance reviews, and schedule adjustments came often, so we kept our scope clearly defined and agreed the extent of each change after confirming requirements with planners, PMs, and server, web, and mobile developers. The project showed first-hand that the direction and communication of decision-makers such as planners and PMs shape how a project goes.

Scope coordination in a large project where planning, PM, server, web, and mobile moved together

Highlights

01

Features linked to account lookup, transfer, product, and utility-bill screens

02

Per-screen exception checks covering input values, button states, transitions, and error messages

03

A clearly defined scope inside a large multi-vendor project

Insights

Read the blog