top of page
Banner.png

A mobile app that helps keep track of and share subscriptions

Synopsis

The Problem

With subscription business models as popular as they are, it’s become increasingly harder for consumers to keep track of their subscriptions. Consumers may get charged for services they aren’t using or trials that have expired. SuSimple has a desktop-only website that helps users track their subscriptions. This (fictitious) company would like to capture a larger audience by developing a mobile app.

The Solution

SuSimple developed a mobile app that helps users keep track of their subscriptions, customize alerts and share their log-in credentials with friends and family. Onboarding and initial set-up is easier than ever as users now have the option to connect bank accounts or credit cards through a secure, encrypted connection.

Interactive Prototype

Go ahead, check it out!

Solution Overview: Primary Features

Subscriptions

Users will feel in control of their subscriptions by keeping track of them in one place.

Sharing

Through SuSimple, users can easily share their log-in credentials with the added benefit of security, quick access and eliminating the need to communicate when passwords get updated.

Custom Alerts

Never get charged for subscriptions that aren't in use or trials that have expired by customizing alerts and setting alert rules.

Reports

Users can get a sense of their spending on subscriptions and compare spending by categories and by month.

Unsubscribe

SuSimple makes it easy to cancel subscriptions by providing a direct external link to cancel a subscription.

My Role

User Experience (UX) Designer

User Interface (UI) Designer

Key Skills

User research, ideating, quickly sketching key frames, wireframes, high-fidelity prototypes, usability testing.

Timeline

Two months

Tools

Figma.png
Miro.png

Background

I received a brief about a fictitious company that has a successful subscription management desktop-only website. They want to increase their market reach by developing a mobile app.

Their User Stories

As a

Current user

Returning user

Consumer

I want to...

see all of my subscriptions in one place

unsubscribe from a subscription

be notified if any of my subscriptions are about to be auto-renewed

so that...

I can get a comprehensive view of my spending on subscriptions

I can reduce needless spending

I can make a decision about if I want to renew the subscription and continue spending money.

Their Current Target Audience

According to the brief, their target audience includes people that are

  • Over 30 years of age

  • They use phone and desktop equally

  • Middle class

  • Trying to be more budget-conscious

Importance of User Research

The information described in the brief are what the company believes their goals and users are. However, it was important to do my own research for a variety of reasons.

  • The user stories may be ones that enforce their business strategy. It’s important to validate them by doing research to ensure that they are also what’s most important or valuable to their users.

  • It may hurt the company’s reputation and it would be a waste of their time and money to design something that isn't user friendly or that no one uses. Reputation is especially important for companies involved in user’s finances.

  • Their target audience may shift as they cater to mobile users.

Process

Design Thinking

2 Design thinking.png

Empathize

Secondary Research

Similar to Lightning Demos in a Google Ventures Sprint, I studied other companies to see how they solved a similar problem. I studied three mobile applications and one website, noting their strengths and weaknesses.

3 Secondary Research.png

Based on this research, one hypothesis I had was that it may be helpful for users to link their bank account to the app so that the app can detect subscriptions. This could lower the barriers for onboarding (no manual entry required), and possibly uncover forgotten subscriptions. However, some users may be weary of giving their banking information away or how their data will be used. This was something I needed to address in my user interviews.

Primary Research

Identifying Participants

I crafted a screener survey and posted it on Slack and social media and emailed and texted it to people I know who use subscriptions. Ultimately, 24 people responded.

Subscriptions

8

average number of subscriptions participants can access

Device
4 66.png

66%

of participants use a smartphone to sign up for, discontinue or manage subscriptions either the same or more than they use a desktop or laptop.

Sharing
5 Sharing 65.png

65%

of participants have access to subscriptions they don’t pay for.

Cancel
6 Cancel.png

74%

of participants have canceled subscriptions in the past 6 months

Reasons for Canceling
7 Reasons.png
Objectives

The principal goal of my primary research was to understand how people manage their subscriptions in order to provide opportunities for improvement. My research questions were as follows:

  • What is the end-to-end process of how people currently manage their subscriptions?

  • What are users’ paint points when they are managing their subscriptions?

  • What are tools or resources people use to manage their subscriptions?

  • What makes users feel comfortable linking their bank account to a mobile app?

Interviews

I interviewed three people individually over Zoom calls, one over a phone call and one in person.

8 primary research.png

Research Synthesis

Affinity Map

After interviewing 5 participants, I listened to their recordings and took notes, making bullet points of important things they said. Using Miro, I put those notes onto digital post-it notes and grouped them into common themes to make an affinity map.

9 Affinity Map.png

Common Themes from Affinity Map

Current Management
Pain Points
Wishlist for App
Trust in Mobile Apps
Tools to Manage
Sharing or Multiple Accounts
Getting better deals

“For me, managing my subscriptions is just managing my passwords so that I can log in to the things“

“I generally have my subscriptions on autopay which is kind of inconvenient. Well, on one hand they are paid timely, but on the other hand [...] I don’t necessarily [cancel them] when I should.”

“If you get a subscription, you put the term in, the day it expires and the app pops up a month ahead saying ‘This is due for renewal. Do you want it?’”

“I’m worried [about giving banking information to apps], but my spouse was the one that signed up in the end.”

“Sometimes I look at iPhone settings [to see subscriptions], but I don’t use it very often because it’s not comprehensive.”

“Sometimes we have accounts that we could be sharing but no one is aware that another person already has an account to the same subscription.”

“[When the intro offer about to expire], I try to call them up and saying ‘I want to cancel my introductory offer. What’s your next introductory offer.’”

Personas

In my interviews, many people expressed very similar ideas, especially over-paying for subscriptions. I knew a variation of this theme needed to go in each persona. From my screener survey I knew that most people have access to more subscriptions than they pay for. It made sense to have two personas: one sharer and one receiver.

10 Marco-Dad.png
10 Greta.png

Define

Key Insights from Research

Tools
Delayed Canceling
Unsubscribing
Duplicate Access
Negotiating Prices
Memberships

Tools people are using for subscription management are inadequate or laborious.

It usually takes a couple of months to cancel subscriptions they are no longer using.

People often
don’t cancel introductory offers before they are billed the full price.

The experience of canceling a subscription can be very difficult or hard to find.

Sometimes, people sign up for subscriptions when they already have access either through family, a friend or through a service provider (i.e. included in phone or cable plan)

People negotiate lower prices for some subscriptions. There are intro offers that existing users can take advantage of.

People wonder if memberships that are meant to save money (Costco, Barnes and Nobel) are worth it.

Problem Statements

With these insights in mind, I was able to define the problem space by creating “How Might We” statements.

How might we...

1

...help people manage subscriptions in a quick and easy way?

...help people have an easier unsubscribing experience?

...help people communicate with their friends or family which apps they have access to?

2

...help people save money?

...prevent people from paying for apps they are no longer using?

...prevent people from paying the full price for apps after the introductory offer?

...help people calculate the price they pay for their money-saving membership is worth it?

...help people get the best price for the subscriptions they want?

Ideate

Once I defined the problems, I went to work brainstorming different solutions. I came up with 38 different ideas or features. In the end, I narrowed them down based on what would be the most useful and what was technologically possible.

User Journeys

Next, I created multiple user journeys to articulate what specific roles a user may inhabit and to keep the user at the center of the design process. I then prioritized them to determine the minimum viable product (MVP).

As a

new user

returning user

subscription owner (payer)

subscription receiver

I want to...

connect banking accounts and credit cards

unsubscribe from a subscription

be notified if subscriptions have changed their price

see trends in my subscription spending

share subscriptions with my family

add passwords and usernames to subscriptions I want to share

see the username and password of a subscription that was shared with me

so that...

I can quickly set up my account.

I can feel in control of my spending on subscriptions

I can save money

I can choose whether or not to renew

I can unsubscribe if it’s too expensive

I have a better understanding of my spending habits.

they can share subscriptions with me and to save them money.

Friends and family can access my subscriptions

I can access the subscription

Priority

Must have

Must have

Must have

Must have

Must have

Must have

Must have*

Must have*

Must have*

see all of my subscriptions in one place

be alerted when a subscription is about to renew

*For a competitive advantage

User Flows

Based on the user stories of the minimum viable product (MVP) and the site map, I assembled user flow diagrams to show how a user would complete their journey. Below is the key and then two of the five user flow diagrams.

Flowchart - Frame 6.jpg
Flow 1: User sets up SuSimple account and connects bank account
Flowchart (3).jpg
Flow 4: User sets up custom alerts
Flowchart (5).jpg

Brand Identify

Before designing for user experience, I developed a brand identity with a company name, logo and some of the user interface style. According to the brief, the brand's personality is that it’s a trusted friend who’s helping users save money. Its attributes are: trustworthy, caring, friendly and casual.

Brand Identify

“Su” stands for “Subscription” and it resembles the word “so,” giving the feeling that this app will make it so simple to keep track of subscriptions. It’s an alliteration that is friendly and has a ring to it. The logo is a filled circle with a concave line. This white concave line is a smile that also mimics the lower quarter of the “S”s in SuSimple. The logo signifies three things:

  • The calmness and contentment the user will feel once they have their subscriptions under control.

  • The encouragement of the brand’s personality–the trusted friend who’s helping you save money.

  • It’s playful because subscriptions are meant to add joy, ease and entertainment to life.

10.5 SuSimple Logo.png

Color

I chose a blue-purple as the primary color and blue as the secondary color because blue signifies trustworthiness and security and while purple signifies compassion, encouragement and wisdom–all traits of a friend who tries to help you save money.

I also took into consideration the color contrast so I could ensure the colors are accessible to a broad spectrum of levels of eyesight and color perception. The primary color has a color contrast of 4.77:1 against white. It's important that the lightest grey and the primary color to have a contrast ratio of at least 4.5:1. I made minor tweaks to the primary color and to Grey 1 until I got there. Based off of the primary color and the lightest grey, I chose four more greys, paying attention to their contrast ratio against the primary color, the secondary color or white, depending on what I thought the colors were going to be used for.  These colors and the way that they are used pass at least WCAG AA standards, but in most cases pass WCAG AAA standards.

Colors, Typography.png

UI Elements

To be able to prototype rapidly, I used a UI kit from RusmirArnutovic.com and modified it to fit WCAG AA accessibility standards at a minimum and to fit SuSimple’s brand.

UI Elements.png

Prototyping

In order to start the prototyping process, it’s best for me to step away from the computer and start sketching with paper and pen. At the same time, I find that users have an easier time assessing a low-fidelity digital version rather than sketches. I knew I didn’t have time to sketch the entire app, then do wireframes. Instead, I sketched key screens using Crazy 8s, then crafted wireframes with the help of the Figma Brainstorming Kit by RusmirArnutovic.com.

Sketches

I used Crazy8s to sketch three key frames. Before sketching, I would note on the side what information could be portrayed in the sketches. Then, I set the timer for 8 minutes and sketched 8 screens.

Wireframes

Below you will find Flow 1 and Flow 4, two of the seven userflows.

Flow 1: User sets up SuSimple account and connects bank account
Frames
11 Wireframes flow 1.png
Video

In the diagram of the userflow, I had the option for the user to log in to SuSimple using their Google account. However, I reconsidered that choice. Since the user has the option to link their bank account, they may not want Google or another large tech firm to have this information, especially considering the media coverage about how large tech firms are using people’s personal information. Therefore, in the wireframe, I didn’t include the option to sign in to SuSimple using their Google account.

Flow 4: Set up custom alerts
Frames
12 Flow 4 wireframes.png

Usability Testing

I conducted the testing remotely on five subscription users in moderated usability studies. The goals of this usability testing were to determine barriers users encounter when they try to:

  • Create an account

  • Set custom alerts

  • Share subscriptions

  • Receive shared subscriptions

  • Get a sense of their own spending habits around subscriptions.

13 Usability Testing.png

Evolution after Round 1: Highlights

I recorded each user testing session. After reviewing the recordings and taking notes, I found improvements that could be made. I’ll highlight two below.

Problem: Creating an account asks for too much information

Context

When creating an account, there are six text boxes to fill out, then users have the option to either link their bank account or manually set up information.

Problems

Some users found six text fields too much to set up an account.

Not everyone understood that there’s an option not to link a bank account. Also, there wasn’t an option to skip this step.

Solutions

I added the option to sign on with Google.

I deleted the need for a username

I separated the buttons to link a bank account and manual set up and gave a short description of each option.

I added the option to skip entering more information. The user does have the option to link bank accounts or manually enter in subscriptions later.

Before
Before 1
After 3

Deleted username

After
After 1
After 2
After 3

Ability to sign in via Google

Separated and explained the two options

Added option to skip for now

Before 2

Problem: Setting up Alerts

Context

When a user would like to set up an alert, they need to move through three screens.

Problems

The flow to set up an alert is too long.

Solutions

I added a shortcut.

Added a drop down menu for users who don’t use the shortcut.

Before
Rectangle 90-1.png

No shortcut

Screen Shot 2022-03-03 at 1.16.png
After
Screen Shot 2022-03-03 at 3.13-1.png
After 2.png

Shortcut is accessed by tapping the three vertical dots on the subscription's card.

Added a drop down menu to set an alert

Prototyping

High Fidelity Prototype

Once I got user feedback on the wireframes, I went to work on the high fidelity prototypes. Below is Flow 1 and Flow 4, two of the seven flows.

Flow 1: User sets up SuSimple account and connects bank account
Frames
14 HiFi Flow 1.png
Video
Flow 4: Set up custom alerts
Frames

Shortcut

15 HiFi Flow 4 v2.png

Drop Down

15 HiFi Flow 4.png
Video

Evolution after Round 2: Highlights

I recorded each user testing session. After reviewing the recordings and taking notes, I found improvements that could be made. I’ll highlight two below.

Problem: Saving Alerts and Adding Multiple Alerts

Context

When creating a customized alert, the user sets their alert using a drop down menu.

There’s space for only one alert to be set per subscription.

The place to set alerts was titled “Alerts.”

Problems

It’s not clear that the alert is saved.

Some users wanted to set more than one alert.

When looking at the accordian menu, some users were confused about what they are being alerted about (are these alerts from the subscription)?

Solutions

I added a “save” button.

People are now able to set multiple alerts.

I changed the header from “Alerts” to “Set Alerts.”

Before
Before1.png
Rectangle 90-1.png

Only able to save one alert

After
After1.png
After2.png

Header changed

Added a "save" button

Now the user is able to add multiple alerts

Problem: Manually entering trial vs subscription

Context

There was the same information needed when a user manually entered a trial offer and a recurring subscription.

Problems

The information the app was asking for didn’t match the reality of the user.

Solutions

I changed the form to manually enter subscriptions so the user selects “trial “or a “subscription”, then more drop down menus appear based on a trial offer or subscription.

Before
Before1.png
Before2.png

"Type" was nested under "Details"

After
After1.png
After2.png
After3.png

First, the user chooses if this entry is a trial offer or a recurring subscription.

Different text fields appear depending on the type of entry

Problem: Reports

Context

Users can navigate to graphs of different months by clicking through a carousel.

Graphs compare spending in different categories.

Labels were as follows: Year to Date; This Month; January 2022; December 2021.

Problems

A carousel doesn’t give the user enough control. Some users didn’t notice carousel.

Users wanted to compare spending from month to month.

Some users were confused by the jump from “This Month toJanuary 2022.”

Solutions

I changed the navigation from a carousel to a drop down menu.

I added a graph so users could compare months.

I changed “January 2022” to “Last Month.” I also think the drop down menu will help solve this problem.

Before
Group 392.png

Before, navigate by carousel

"January 2022" follows "This Month"

After
drop down.png

Navigate by drop down menu

new graph.png

Option to include yearly subscriptions

Graph added to compare months

Final Prototype

Learnings

Leverage Powerful Tools

I took the time to learn about autolayout and interactive components. Although it took time away from prototyping, in the end it saved a lot of time, preventing me from building out multiple unnecessary screens. This is particularly apparent in the drop down menus and accordions in the screens with the details about individual subscriptions.

Have Fun with Animation

I intentionally animated a couple of key elements like snack bars confirming a user’s action, a spinning loading icon, and smart animating alerts for the user to finish setting up their account. I don’t believe this is expected in a prototype and it delighted my usability participants.

Recruit Participants Early

I learned that it’s important to recruit participants far before the prototype is done. First, it helps me stick to my deadline. Second, it saves time by allowing me to move from building the prototype to testing without having to wait.

Thank You!

bottom of page