Videos for everyone
Project context 
Founded in 2015, Coverr has been on a mission of providing high-quality free stock videos for content creators. 
As the user base grows, we see a need to enable personalization and to have a centralized space for creators to organize their video collections on Coverr. This understanding yields the creation of the user account - a signed-in state of Coverr. 
My role with Coverr is to lead the sign-in state's design vision and enable the team to start experimenting with increasing understanding of our user types.

North Star
Before breaking down to releases, my process is to clarify our north star, the long-term vision, so the team does not lose sight of the final goal. 
For user accounts, our north star is to arrive at a state where users have public pages to showcase the collections they created. We will be measuring their asked and observed attributes. Asked attributes mean any explicit questions we ask our users; Observed attributes are behavioural signals we pick up from our users. Based on their asked and observed attributes, we will show then be able to surface personalized recommended videos (and later on, any new verticals). 
Project goal
For V1, our goals are: 
- To map out different user types and start correlating them with the preferred video type/ theme to identify a pattern. 
- Define the informational architecture and the hierarchy of the user account 
- Design the infrastructure of the signed-in state experience and the user account, both UX and UI. 
- Identify key areas for the team to start testing
Current users
Today, we categorize our current users into 3 categories: Content creators, designers/developers, and educators from previous research. 

However, we have yet to understand much about each group's preferences and workflow in Coverr. To empathize with the users, I decided to start with user stories. These can serve as hypotheses that can be later tested against.

User stories
- As a content creator, I would like to mark/subscribe to my interests in order to get more relevant content from Coverr for my future projects.
- As a developer, I would like to be able to manage the API keys that I use for different projects in one place. 
- As a developer, I would like to be able to check on the progress of the API key approval. 
- As an educator, I would like to save all the videos into different categories so I can come back and access them later with ease.

Hypotheses 
From the user stories, here’s a list of hypotheses that we have for the user account: 
- We believe by offering users self-served access to Coverr’s API limited tokens we will see an uptick in apps trying and using our API, less admin work and more requests for unlimited production API keys.
- We believe by allowing users to create collections in their user account, we will see an increase in returning users. 
- We believe by surfacing personalized content, we will see an increase in user downloads.
User flow 
As this is a brand new flow we are introducing to enable future learnings, the main flow is the sign-up flow that leads to the user account.
What’s the next step 
This project's business impact is to increase user retention and 2nd session. Currently, we are still gathering data before drawing a conclusion. 

In this project, new components are being introduced to Coverr's ecosystem. Although there was a rudimentary component library, I noticed the need to start building out a design system to enable the team to work faster. 
Back to Top