EPILOGUE

ROLE
Solo
TIMELINE
February 2026 – June 2026
TOOLS
Figma
Adobe Fresco
Pen and Paper
SKILLS
UX Research
UI Design
Problem
Many readers lose motivation for reading at some point, eventually going days, weeks, or even months without picking up a book. In the end, readers have a hard time reconnecting with old books or finding new books they would enjoy.
Solution
Epilogue shows personalized recommendations, lets readers track and review their books and set reminders reminders to stay on track with their reading. These features help readers stay motivated and build a consistent reading habit.
Empathize
Getting to know the users I’m designing for
I conducted user interviews to understand the participants' reading journeys, what might cause them to fall into reading slumps, and general pain points throughout their journey.
Number of participants
12
Location
Toronto, Canada
Age group
20-25 years
Interview format
Virtual & In-person
All 12 participants had 3 things in common
From the user interviews, I found three pain points that all the participants had in common. I saw a lot of these pain points in my initial research, further helping me understand the problem on a deeper level. The pain points also provide some insight into what I want to focus on solving.
Decision Fatigue
Too many books out there, leading to participants not chosing any books.
Burnt Out
Readers read a lot of books at once and eventually get burnt out.
No Reading Routine
Readers can forget or struggle to prioritize reading in their free time.
Readers need some sort of way to be engaged with reading.
Creating user personas to futher empathize with users
From both primary and secondary sources, I now have more context and connection with my future users. I want to personify the information I collected so far through user personas.
I created two user personas: Sofia and Liam. These personas represent two main groups of users whose goals and frustrations align with the 3 common pain points I discovered. Both Sofia and Liam love reading, but they experience different frustrations that cause them to fall into reading slumps.


Noting down some strengths and weaknesses across other app
I also researched other apps on the market. Doing a competitive audit helped me understand their strengths and weaknesses, as well as what users liked and disliked about them. This was important because it showed me what worked, what could be improved, and how my application could offer a better experience.
I didn’t limit the audit to just reading apps. From my research so far, I knew users needed help finding recommendations, pacing their reading, and remembering to read. So, I also looked at other apps to see how they addressed these frustrations.

The audit showed that while most apps support the primary goals,
they often feels outdated, cluttered, or overwhelming rather than engaging.
Define
PROBLEM STATEMENT
I needed one statement that summarized the main problem I was trying to solve. Using what I learned from my user interviews and personas, I created a problem statement that focused on the main frustrations readers were facing:
Finding books to read is often overwhelming and discouraging. How can we help readers discover books they'll enjoy and build consistent reading habits?
GOAL STATEMENT
Now that I knew the problem I wanted to solve, I needed to define the main goal of the app. I focused on the goal, the impact, and how I would measure it's success. This gave me a foundation for future design decisions and helped me stay focused on the users’ needs and frustrations that I was trying to solve.
My product will help readers discover personalized book recommendations, making it easier to build consistent reading habits and overcome reading slumps. Success will be measured through user engagement, reading consistency, and goal completion.
Ideate
Exploring 8 designs in 8 minutes
Once I had a rough idea of the pages I wanted, I set an 8 minute timer and sketched 8 different screens. This helped me visualize my ideas without focusing too much on the details.

Users preferred writing book reviews over tracking goals
I did a quick, informal user testing session with my 12 participants. The goal was to get feedback on my Crazy 8 sketches and the pages I was thinking of including in the app. Since this was an informal session, I didn’t use any metrics to measure success.
I asked participants for their thoughts on the pages, what they liked, what they didn’t like, what else they would like to see, and what could help readers avoid falling into a reading slump.
58%
of the participants didn’t want a goals page because it could make reading feel discouraging.
75%
of the participants suggested a rating/review page to reflect on books they finished.
⭐
If I were to do this user testing again, I would use metrics to better support my design decisions at this stage.
Eg. track how many participants found each feature useful or ask them to rank which features they would be most likely to use
The goal statement needed to be changed based on user feedback
BEfore
My product will help readers discover personalized book recommendations, making it easier to build consistent reading habits and overcome reading slumps. Success will be measured through user engagement, reading consistency and goal completion.
after
My product will help readers discover personalized book recommendations, making it easier to build consistent reading habits and overcome reading slumps. Success will be measured through user engagement, reading consistency.
Mapping out the user's journey
Based on the new goal statement, I mapped out the primary user flow through the app.

Turning my ideas into something more refined
I had a lot of rough sketches and ideas, but I needed to organize them into something more structured. Using my Crazy 8s as a starting point, I went back to pen and paper to create my paper wireframes.
These paper wireframes were the basic structure of my designs, showing only the main content and features I wanted on each screen.
I then used my paper wireframes to create low-fidelity designs in Figma. At this stage, I focused on the layout and main components without worrying about details like colours, icons, or styling.


recommendations page
[where users can swipe to add books to their library]


library page
[Where users manage their reading list and track books they’ve read]


Journal entry page
[writing a new journal entry]


Setttings page
[to set reading reminders]
Evaluation & Iteration
Time to start with the high-fidelity designs
After refining my low-fidelity designs, I moved on to high-fidelity designs. I used my updated prototypes as a starting point and began exploring the look and feel of the app.
I wanted to keep the interface clean and simple, since my research showed that readers already felt overwhelmed when choosing what to read next. I didn’t want the app to add to that.
I also named the app Epilogue. I thought it was fitting since an epilogue of a book is a short continuation of the story, similar to how this app allows users to continue reading after completing (or not completing) their latest book.

Doing user testing with the hi-fidelity designs
Once I had my high-fidelity prototype ready, I moved on to testing the prototypes. I went back to my 8 participants, walked them through the testing process, and asked them to complete a series of tasks.
At the end of the session, I asked each participant to fill out a questionnaire to help me measure the success of the app. The questions were based on the goal statement and they helped me see how well the final design supported those goals.
6/8
of the participants were very satisfied with finding new books recommendations.
4/8
of the participants found it slightly easy to keep track of their books.
6/8
of the participants found it easy to create and write book reviews.
8/8
of the participants found it very easy to set reading reminders.
Overall, 75% participants were satisfied with the hi-fidelity prototypes before the final iteration of changes.
Bringing user feedback into my high-fidelity designs
After collecting quantitative data from the testing session, I made one more round of updates to my high-fidelity designs.
One thing I missed earlier was updating the undo button, so I made sure to address it in this final iteration.



Final Screens
Swipe & Discover
Swipe to find your next favorite book. Tap the Heart to save it to your Library, or the X to skip.
Library
Keep every book organized from To Be Read to Completed. Update your pages as you read and mark a book finished when you're done.
Journal
Capture your thoughts on every book you read. Write reviews, leave a star rating and keep a personal record of your reading life.
Setting Reminders
Set notification reminders to remind you to read. Choose a time and a message, and make reading a daily habit.
Reflections
What I learned
I learned the importance of using user research to back up my design decisions. I didn’t have to rely on assumptions because I had the opportunity to conduct multiple user interviews and gather metrics.
Challanges I faced
During the initial stages, I had a lot of ideas, and it became a bit overwhelming because I wasn’t sure which direction to take. I reminded myself that I couldn’t create an app for every reader, so I narrowed down my ideas and kept my goal statement in mind.
What I see for Epilogue's future
There are so many more features I would love to add to Epilogue. For instance, I could add an AI chatbot that recommends books based on the user’s library. I’d also love to expand Epilogue to connect users with others who are in a reading slump, creating a more social experience.

