Children’s Digital Library Application

My Role

Tiny Tales is an app for parents to use with their children in reading books together. However, users reported that they had a hard time finding good new books to read to their children. I set out to create a natural way for users to discover books everyone would enjoy, and that would make Tiny Tales a primary reading source for families.

While maintaining focus on the needs of the users, I completed a one week design sprint following the steps outlined by GV to solve this problem. By the end I designed an effective prototype that solves the problem users were having of finding relevant books.

As a parent myself, I related to the users as it can be difficult to find quality and engaging books for children. I wanted to design a product that would feel familiar to parents and would require very little learning to use.

The Problem

For my prompt I was given some information that was collected during previous user research. Upon reading the research, I identified that all parents wanted different topics or types of books, all at different times. It was also important for them to find new books during quiet scheduled reading time, as well as during the stresses of reading a book at bedtime.

I took the information given to me and formed this “How Might We” question to help guide my design sprint:

A Map to the Goal

Using my HMW question as my end goal, I created a map for users to take in selecting a new book to read. I felt that users would need a simple way to learn about a book before selecting it to read, so I included using a pop out in my map to accomplish my end goal. My map is simple, but efficient.

Following the next step of a design sprint, I completed a modified lightning demo to understand what other companies have already created. With my HMW question in mind it was important to look toward similar types of programs that parents might interact with on a regular basis so they will already be familiar with Tiny Tales upon first use. I focused on looking at streaming services, digital libraries, workout apps, and others. The following are a couple examples of my findings.

Lightning Demos

Netflix: Contains a large library and movies are categorized for the user to easily find what they are looking for. The thumbnails of each show are large and draw attention making it very easy to browse selections.

Audible: In this screenshot of the “Discover” page, the CTA is to use category buttons on the top of the page to help the user find what they are looking for quickly. These can also be things that users regularly search for. These links or buttons on the homescreen ensure the user is able to find and locate new books quicker. 

Sketching It All Out

Upon completion of my lightning demos, I sketched out a few possible solutions using the Crazy 8s method. Before beginning, I thought I already knew what I wanted to do for my solution sketch, but by using this method I was able to get past these initial ideas and come up with some new ones. For example, I initially was planning to design my app in landscape mode for a tablet. However, while doing Crazy 8s I realized that portrait orientation seemed more natural for users and easier to layout for design.

Crazy 8s

Solution Sketch

My critical screen for this design sprint is the browsing page where users start to find a new book. Combining my findings from my lightning demos with my ideas from my Crazy 8s I sketched my solution focusing on my HMW question. Below you can see the homepage of my browsing tab to find new books (B), as well as the “My Library” page (A), and another page of what it might look like to tap on a book a user is interested in (C).

Returning to my solution sketch the following day, I realized that I needed to change a few things, such as differentiating the search function and browsing page, but overall I had a solid base. I then created a storyboard that my users would follow and I was finally able to see my app start to come together in a great way! I believe including things like the category buttons at the top of the browsing page really allows parents to find what they are looking for quickly and easily.

Making Decisions

I created my prototype using the program Marvel. I chose to use this program because although the design tools are limited, it allowed me to quickly design a functioning prototype to test with users. 

While creating the prototype, I refined a few design elements from my storyboard, such as creating a button to add a book to “My Favorites” or putting a search bar at the top of the browse tab. I created a professional prototype that appeared and felt like a fully developed app. I felt confident that this app would allow parents to easily find new quality books.

Prototype the Program

Click here to view the Final Prototype

I interviewed five different people who are all parents of young children. I recruited these five users to test my prototype by contacting neighbors and friends who I knew had young children. They were all willing to test the prototype and gave me great feedback.

Overall it was a very straightforward interview process. All testing was done at the participants house, and each interview lasted 15-20 minutes. I asked each person about their reading habits with their children, their expectations with an app aimed at reading stories with children, and for any feedback on my prototype once they tested it.

Test Day

These findings caused me to really stop and think about who this app is directed toward, and how it would be used the majority of the time. I came to the conclusion that parents would still be the primary users of the app, but I did need to make it a little more colorful and exciting for the children using it with their parents. I made the necessary changes in my current iteration of the prototype.

A couple users in testing mentioned that they would want to use the app as a tool their older children could use in their reading practice. Moving forward I would continue to modify the design the app so that as children grow they could learn to use it by themselves. For now, I have made some small changes to my current prototype by adding more colors, adding more patterns and making it more child-friendly. 

Adding colors, but in more subtle hues allows the app to appeal to children and adults equally. I also made the icons of the books as rectangles instead of squares so it more closely resembles a book cover. These little changes make it easier for the users to navigate the app.

Implementing Feedback

For TinyTales, I feel like I successfully completed the goal of my HMW question. I was able to design a tab in the app that allows parents to easily and quickly find new books. It uses similar design elements of other programs that parents know and love. I would continue to add more fun pictures or icons with buttons and titles to appeal to children, but currently I believe this iteration of the app solves the current problem of parents needing an easier way to find new books to read with their children.

Following the five day steps of a design sprint taught me how quickly an idea can come to fruition. Not only any idea, but a well thought out idea that can truly be tested in low fidelity. I also learned that I think design sprints would work great in certain situations, such as creating smaller changes or features with an already developed app, but larger, more detailed projects I believe require more research and design. Methods such as the Crazy 8s and storyboarding are practices I will apply to future UX projects.

Reflecting & The Future