Scriber
Introduction
Nowadays with multiple companies creating subscription-based products, people tend to have a plethora of subscriptions to keep track of. They see money deducted from their accounts for the services but might not realize it could be a subscription they don't want or need. Scriber has created an app to manage all subscriptions detailing spending data, upcoming payments, and an easy to see list of current products.
Project Info
Duration: 2 Weeks
Key Skills: Ideation, User Flows, Information Architecture, Sketching, Wireframing, Visual Design, Prototyping
Prototype
Explore the Hi-Fidelity prototype,
click below:
Easily manage your subscriptions in one place.
Design Process
I. Discover
Problem Statement
User Insights
Competitive Analysis
User Flow
II. Ideate
Low-fidelity Wireframes
III. Validate
High-fidelity Prototype
Usability Testings
Problem Statement
Scriber is currently a desktop-only website and needs to create a mobile version for a broader audience. Although successful with their current version, they understand a mobile-friendly product will significantly increase their market reach-- which will ultimately result in an increase in users and added business.
User Insights
Key highlights from the user interview:
​​
-
As a current user, I want to see all of my subscriptions in one place so that I can get a comprehensive view of my spending on subscriptions.
​
-
As a returning user, I want to unsubscribe from a subscription so that I can reduce needless spending.
​
-
As a consumer, I want to be notified of auto-renewed subscriptions so I can make better spending choices.
​
I. Discover
Competitive Analysis
I conducted a competitive analysis on other apps that created a similar product. From research, I gathered what made them successful and what needed improvement. Through this information, I was able to start forming Scriber's mobile-friendly app.
User Flow
Here is a possible end-to-end experience a user might go through.
II. Ideate
Low Fidelity Wireframes
After conducting research I began working on the low-fidelity prototype. Once this was finished, I ran a quick usability test to get feedback from users and to test if everything was intuitive so far.
Dashboard​​
​
Subscriptions
Adding Subscriptions
Autofill
Analytics​
Subscription Details
Cancelling Subscription
Sucess​
III. Validate
Hi-Fidelity Frames
After receiving feedback on my low-fidelity prototype, I moved on to the hi-fidelity screens and created a prototype.
Dashboard
Get a snapshot of your spending, upcoming payments, and recent payments. Users are able to see their weekly, monthly, and yearly spending with a click of a button. Users can also see how many days are left to pay.
Subscription List
Here, users can easily manage and add subscriptions. It also provides visibility on spending. With one click, users are able to view details and unsubscribe from any unwanted subscription.
Reminders
Scriber lets users know when their next payment is due and allows users to set a reminder. Having the option to set a reminder means users never miss a payment and gives them time to make decisions on their subscriptions.
Spending Tracker
Having the ability to see a breakdown of spending allows users to make smart decisions. Scriber makes managing subscriptions easy.
Usability Testing
There were ten participants that tested the prototype. Seven were given a few tasks to complete. The other three were given free rein to explore the app for first impressions and feedback.
​
Key findings during the tests:
-
100% of the participants were able to complete the tasks given at hand
- Task:​
-
Look at your spending from previous months
-
Add a new subscriptions
-
Unsubscribe from Crunchy Roll
-
- Task:​
​
First Impressions:
-
The app looks clean and liked that things are clearly labeled
-
Liked that the reminders tell you how many days left
-
The design is intuitive and easy to navigate
​
Feedback:
-
Participants liked that they were able to see their spending weekly, monthly, and yearly
-
A participant suggested having more graphs and possible in-depth breakdowns of the spending
-
Having the ability to sort subscriptions would be nice
Conclusion
Lessons Learned
-
Using other research methods along with what I have already done would have given me more in-depth information. If I had more time I would have loved to try other methods of research and testing to get different insights and results.
​
-
Having a larger testing pool would have given me more insight into all types of users. I mainly stuck to users in their early thirties. Having a wider range of ages and backgrounds to test from would allow me to create an experience that is intuitive to all and reaches a larger target audience.