uxtribe
Published in

uxtribe

Students redesign Swedbank’s mobile banking app UX

How we identified, prototyped and tested two UX improvements for a popular mobile banking app.

Leading by example

UX students in action.

Why Swedbank’s banking app?

The Problem

Swedbank mobile application — payment view

But first — why are some apps confusing?

Pain Point #1
Making and requesting payments

Revolut user flow vs Swedbank user flow

Hypothesis #1
Simpler = better

Our first hypothesis was: a simpler user flow (aligned with user mental models) would be easier for users to navigate. An easier flow makes it easier to send and request money.

Hypothesis #2
Users don’t understand

Swedbank’s mystery turquoise icon

This is where our second hypothesis came into play: the button’s meaning is impossible to understand.

Swedbank’s mobile app results screen

Hypothesis #3
Well constructed auto-suggestions improve app usability

Revolut results screen

Pain point #2
Finding a payment in ‘payment history’

Hypothesis #4
Pagination is better than infinite scrolling

To recap, our hypotheses were:

Student prototypes + solutions

Solution to Pain Point #1
Making and requesting payments

Swedbank payment screen vs students prototype

Solution to Pain point #2
Finding a payment in ‘payment history’

Infinite scrolling vs Pagination

Survey

1. What purpose would you use this screen for? (Current app)

2. What would you tap to request a payment? (Current app)

3. What would you tap to request a payment? (Prototype)

4. If you search for a payment made a month or more ago, how would you describe this process?

Usability testing

A student conducted a usability test

Conclusion

Here’s what some of the students had to say about the exercise:

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store