UX Case Study

Orchard

Responsive web app for mobile payments

Compared to Apple Wallet, Orchard improves how users select a specific credit or debit card.

My roles
User Research

Information Architecture

Experience Strategy

Interaction Design

Branding and UI

My tools
Figma
Figma

UsabilityHub.com
UsabilityHub.com

Miro
Miro

My UX design process

Step 1.
Conduct initial user research
Step 2.
Create user stories, personas and user flows
Step 3.
Draft and link low- and mid-fidelity wireframes
Step 4.
Conduct user preference and usability testing
Step 5.
Develop and apply visual brand language
Step 6.
Finalize UI design and prototype
Step 1.
Conduct initial user research
Step 2.
Create user stories, personas and user flows
Step 3.
Draft and link low- and mid-fidelity wireframes
Step 4.
Conduct user preference and usability testing
Step 5.
Develop and apply visual brand language
Step 6.
Finalize UI design and prototype
Overview

The problem

Apple Wallet's inefficient selection process

Overlapping cards result in narrow tappable areas. Users often get frustrated having to try more than once to correctly select an intended card.

The problem statement

How might we make the card selection process more accurate to reduce user frustration?

The solution

The Orchard difference

Full images and much larger tappable areas help users more quickly and accurately pick their intended card from a scrollable list.

Step 1: Initial User Research

Is it really a problem? YES

To ensure the problem was real before spending time on a solution, I conducted a brief user study which confirmed the inefficiency of Apple Wallet.

Methodology

Type: User phone interviews and affinity mapping of responses

Participants: 3 Apple Wallet users recruited from friends and family

Timing: 7/4-7/5

Goals

  1. Validate that selecting a specific card is a frequent and inconvenient problem with Apple Wallet
  2. Confirm convenience as the most important user benefit of e-wallets
  3. Explore why users have multiple credit/debit cards and bank accounts
Initial responses by participant grouped as Behaviors, Needs, Frustrations and Quotes
Affinity mapping of all responses

Key findings summary

  1. Selecting the wrong card happens a lot and detracts from the primary benefit of convenience
  2. Universal agreement that convenience is the most important benefit
  3. Reasons users have multiple credit/debit cards and bank accounts
    • Improve credit score
    • Build up available credit for emergencies
    • Finance large purchases
    • Receive a discount for signing up or when used in a particular store
    • Earn rewards, miles, and/or cash back
Step 2: Create user stories, personas and user flows

Keeping user needs front and center during development

I developed user stories to ensure that the universal and differentiating features I would be building into the e-wallet would deliver actual value to users based on their needs.

As an e-wallet user, I want the flexibility to use a credit card, debit card and/or my bank account for any particular purchase.

As someone concerned about the security of my identity and financial information, I want a quick and secure way to log in.

As a frequent shopper and sender of money, I want a simple and easy-to-use home screen, so I can access and use each function quickly.

As a user seeking to make purchases and transfers to many parties and through many types of accounts, I want an e-wallet that supports all of my financial options.

As a frequent shopper and e-wallet user, I want an easier way to select a specific card or account for a specific purchase.

As a new user, I want to be able to create my account and enter my first card/account information quickly, so I can start using it.

As a user seeking to consolidate my financial tools, I want a single app that allows me to make purchases, send money and request money.

As a user with a lot of cards and accounts, I want to see all of my cards/accounts in one place so that I can select the best one to use for any given transaction or request.

Step 2: Create user stories, personas and user flows

Crafting a deeper understanding of users

To maintain a focus on target user needs throughout the design process, I created a proto-persona and user journey based on insights from my previous user interviews.

Jared: High-frequency e-wallet user

29 year old financial analyst in Chicago, IL. Single. Uses Apple Wallet on iPhone, iWatch and MacBook Air. Uses his e-wallet for almost every purchase because of the convenience and speed.

Transaction frequency: Online: 1-2/week; In-store: 2-3/day

Frequent transactions: Morning coffee stop; Lunch with colleagues; Weekend dates

Step 2: Create user stories, personas and user flows

Plotting the payment user flow

I developed the following user flow for completing a transaction to inventory the necessary screens to help users.

Step 3: Draft low-fidelity wireframes

Roughing out the basics

To start visualizing app functions and my differentiated card selection process, I sketched numerous wireframes, including the following payment flow.

After a user unlocks the phone and signs in to the app, the home screen displays
Card Select screen features a vertical scroll of full views of each card making it easier for the user to correctly select a specific card
Face ID activates to validate user and authorize the transaction while displaying the selected card/account
Once verified, user is instructed to hold mobile device near the NFC reader
User receives confirmation that the transaction is complete
Step 4: User Preference and Usability Testing

Do users prefer the Orchard solution? YES

My previous user research confirmed that an inconvenient problem exists. This research showed user preference for my alternative approach.

Methodology

Side-by-side testing via UsabilityHub.com of mid-fidelity wireframes

Participants: 15 adults from US, 2 from Germany, 1 each from Canada and Switzerland

Timing: 8/20-8/26

Goals

Before spending any more time on development, it was important to see if users preferred my alternative to Apple Wallet.

Key finding: 74% of respondents preferred my alternative

00%

A version similar to Apple Wallet's stacking of credit and debit cards on each other

00%

The Orchard alternative: A full view of each card, plus a text label

Preferred by 74% of respondents

Respondents that selected the Apple Wallet option stated it was mainly because of their familiarity.

Those that selected my alternative confirmed it’s difficult to tap the right card in Apple Wallet, how they prefer to see a whole card, and how they anticipate fewer selection mistakes because of the separation between cards.

The comments about my alternative exactly match the purpose of the app: an easier and more accurate way for users to select a specific card for a purchase — providing strong validation for continuing development.

Step 4: User preference and usability testing

Is Orchard easy to learn and use? YES

Methodology

Online moderated sessions using a mid-fidelity prototype

Participants: 5 adults from US, 1 from Germany

Timing: 8/30-9/4

Research goals

With Orchard being new to the market, a primary goal was assessing Orchard’s learnability by first-time users

Inform UX refinements by uncovering user issues during common digital wallet tasks (e.g., making a purchase, sending money)

User tasks

Create an account (core function)

Transfer $15 to a friend (core function)

Make a purchase with a specific card (differentiating function)

Make another with a different card (differentiating function)

Raw notes from the usability testing
Clustering of participant responses in Miro

Analysis process

In Miro, I first clustered by topic all raw notes and observations

Using a Rainbow spreadsheet, I assigned all user issues an error rating based on Nielsen’s 4-part scale and created an official usability test report

Key findings

High utility and usability based on user success with the tasks and their positive feedback

User issues and improvements are detailed in Step 6 below

Step 5: Develop and apply visual brand language

Evolution of selection screen UI from concept to completion

Step 5: Develop and apply visual brand language

Evolution of the home screen UI

Step 6: Finalize UI Design and Prototype

Additional app screens

You've seen it.
Now explore it.

Retrospective

A look back...and forward

A rewarding experience

Early-stage validation of a potential problem with Apple Wallet fueled my drive to then design a superior solution.

Getting objective validation that my Orchard solution was far more preferred by users was also very fulfilling.

Two challenges

One challenge was creating a vibrant interface that was still streamlined for quickness. The Orchard color palette and singular backgrounds provided a compelling user experience without distracting users or resulting in long load times

A second challenge was iterating the color palette to increase accessibility, because my original orange/white and teal/white combinations were not. I had to skip the orange/white combo for critical text and buttons, and I darkened the green to be more accessible.

Initial ideas for future improvements

  • Dark mode option
  • Display user-selected info about each card, such as the discount, cash-back or mileage bonuses
  • Testing of a horizontal scrolling card select process

The work isn't
going to do itself.
Let’s talk.

Want to explore a little more?