After conducting in-depth interviews with our users in order to get insights into how the uLesson app was being used, we were able to determine that one of our greatest barriers to customer retention at uLesson was the lack of availability of constant internet connection to watch our learning videos uninterrupted.

Also, the constant data required to stream the videos was increasing costs and made the platform more expensive for the average user.

One of the solutions proposed was to include downloads feature that will enable students to download videos so that they can watch later.

Because our direct users were kids and the way the uLesson library was structured I had to highlight and cater to peculiar problems that could arise while our users tried to access the download feature. After brainstorming with the team, I was able to highlight 3 major stumbling blocks we needed to work on. These are:

The video library of the uLesson app is divided into Chapters → Quests → Videos. We decides to establish what point users can download videos and how they should show up in the downloads homepage in order to minimize confusion.

After brainstorming, we decided to allow users download videos at any point in the heirachy i.e they can download videos, chapters or quest but only the chapters would show up in the downloads tab. Quests would show up under videos and videos will show up under quests.

From user research and feedback, we realized that phone storage was going to be a common issue among most of our users as most of them were using devices with RAM sizes between 4 -16GB. I then designed the feature allowing users to manage their storage and allocate storage for uLesson videos on their devices.

I decided to make downloads available from the chapters, quest and video levels so that our users can download videos from any point during their journey. One of the major issues I encountered was making the downloads for the quest as intuitive as possible.

I came up with 3 different iterations for the download button and tested it with a small sample size of my test group before finally deciding on the final design.