Designing a reading app for habit formation
Timeline
4 weeks
Tools
Figma, Miro, moderated usability tests
Platform
Mobile, iOS
Role
Sole product designer
Overview
Many adults want to read more, but professional responsibilities, mental fatigue, and easier forms of entertainment often prevent that intention from becoming a consistent habit.
I designed Readit to reduce the effort required to begin. The experience helps readers set manageable goals, continue their current book, record reading sessions, and see evidence of their progress over time.
My Role
I independently led the project from discovery through final design. I conducted user interviews, translated behavioral insights into product strategy, defined the core experience needed, and designed the end-to-end mobile experience.
The challenge
People often set ambitious reading goals but struggle to maintain them when work, mental fatigue, and everyday responsibilities compete for their attention.
My initial assumption was that a reading product would need traditional gamification to make the activity more engaging. Discovery research challenged that assumption.
Participants were already motivated by the experience of reading. What they lacked was a low-effort way to begin and a supportive system for maintaining consistency.
The challenge was not simply to design another book tracker. It was to understand what prevents someone who already values reading from actually beginning a session.
Problem
How might we make it easier for busy adults to begin reading and recognize their progress without making reading feel like another task they have failed to complete?
Research
I conducted 3 moderated conversations with adults ranging from frequent readers to people who wanted to read more consistently. The research focused on three questions:
- What motivates people to read?
- What prevents them from reading as often as they would like?
- What types of structure feel supportive rather than restrictive?
I organized responses through affinity mapping and looked for repeated patterns across participants’ behaviors, motivations, and frustrations.



Key insights
Intention was not the problem
Participants already understood the value of reading and often described it as relaxing, immersive, educational, or an escape from everyday stress.
They did not need to be convinced to read. They needed help turning that intention into an action.
Mental energy mattered
“Not having time” often represented a broader problem. Even when participants technically had free time, burnout and decision fatigue made starting a book feel difficult.
Readit was therefore competing less with other reading applications and more with the low-effort alternatives available at the end of a demanding day.
Need structure without pressure
Participants responded positively to reminders, visible progress, and manageable goals, but they did not want reading to feel like work.
This created an important tension: the product needed to encourage consistency while still allowing users to read at their own pace.
sense of accomplishment
Users wanted to read at their own pace but needed gentle, structured nudges. They desired a way to see their progress visualized, as this provided a sense of accomplishment that counteracted their daily stress.
Reframing the opportunity
The research shifted my focus from maximizing engagement to minimizing activation energy.
Instead of asking:
How can I make reading more entertaining?
I began asking:
How can I make starting feel easier?
I began asking:
How can I make starting feel easier?
This reframing changed the direction of the product. Features were evaluated based on whether they reduced the effort of beginning, supported a flexible routine, or helped readers see evidence of their progress.
Translating research into a focused product
Reduce the effort of starting
A returning reader should be able to continue their current book and begin a session with as few decisions as possible.
Support flexibility over perfection
Goals and reminders should provide direction without punishing users when life interrupts their routine.
Make progress visible
The product should recognize small accomplishments rather than only celebrating completed books.
Keep reading at the center
Tracking, organizing, and goal setting should support the reading experience rather than becoming the experience itself.
Personas
I translated the repeated behavioral patterns from the interviews into two personas that helped me evaluate feature priorities and design decisions.


Defining the MVP
I prioritized the minimum experience needed to support a repeatable reading habit. The MVP included book organization, reading goals, timed sessions, and progress tracking. Recommendations, community challenges, social sharing, and extensive journaling were left for later because they did not directly reduce the difficulty of beginning a session.

Core user flow
The core experience begins from the home screen, where readers can continue an existing book or add a new one.
After selecting a book, they can begin a timed reading session. When the session ends, their reading time and book progress are saved and reflected in their daily and long-term goals.

Design Exploration
I began with low-fidelity wireframes to determine the hierarchy of the home screen, the structure of onboarding, and the steps required to begin and complete a reading session.
The early explorations focused on three questions:
- What information does a reader need before beginning?
- How much setup is necessary before the product becomes useful?
- Which actions should remain available without distracting from the reading experience?

Key design decisions
1. Make starting immediately accessible
The home screen brings the reader’s current book, daily progress, and primary continuation action into one place.
Instead of requiring users to browse their library each time they return, the experience provides a direct path to continue the book they are already reading.
Broader statistics remain available, but they support the primary action rather than competing with it.


2. Make setup manageable
The onboarding experience breaks setup into a series of focused decisions rather than presenting one long form.
Readers can choose a daily reading target, establish a yearly book goal, select a preferred reminder period, and add their current book.
Predefined goal options reduce decision-making, while custom options preserve flexibility. Adding a book can also be skipped, allowing readers to explore the product without completing every setup step.
3. Provide flexible structure
Readers have different routines. Some read in one long session, while others read in short periods throughout the day.
Instead of requiring an exact schedule, Readit introduces flexible reminder periods such as morning, midday, and evening.
The reminders are treated as optional support rather than a requirement for building the habit.
In a production version, I would test whether broad time periods provide enough control or whether readers need adjustable recommended times within each period.


4. Measure smaller forms of progress
Streaks can motivate readers, but they can also create guilt when a routine is interrupted.
I avoided language such as “Don’t break your streak” and designed completed-goal moments around encouragement rather than urgency.
The product recognizes consistency while allowing readers to return after a missed day without framing the interruption as failure.
Solution
Readit connects goal setting, book organization, focused reading sessions, and progress tracking into one cohesive experience. Readers can establish a manageable routine, return directly to their current book, record their reading, and see how each session contributes to longer-term goals.








Usability testing
I conducted moderated usability sessions with three participants who represented different reading habits and levels of consistency.
Participants completed the primary experience, including onboarding, setting reading goals, adding a book, navigating their library, starting and ending a reading session, and reviewing their progress.
The sessions confirmed that participants understood the core concept and found the experience straightforward. They also revealed areas that would require further iteration before development, particularly around information hierarchy, goal flexibility, adding books, and completing a reading session.
3 participants
6 core tasks
4 prioritized opportunities
Findings
Make session completion more explicit
Two participant were unsure what information to enter at the end of a session and whether “Done Reading” would save progress.
Next step: Clarify the ending-page field, distinguish optional actions from required information, and test whether “Save Session” is a clearer primary action.
Simplify adding a book
Participants liked the scanning concept but were not always sure where to add a book or which category it would enter.
Prioritize the current book
Participants looked first for their current book, daily progress, and the next action they could take.
Next step: Increase the prominence of the current book and “Continue Reading” action while reducing the visual weight of secondary statistics.
Clarify goals and reminders
Participants had different routines, and some were unsure whether a goal represented time, pages, or completed books.
Next step: Clarify the unit attached to each goal and make reminders more flexible and optional.
Outcome and next steps
Within four weeks, I designed and tested an end-to-end mobile prototype covering onboarding, goal setting, book organization, timed reading sessions, and progress tracking.
Testing confirmed that participants understood the core concept and identified four priorities for the next iteration: improving the home hierarchy, clarifying goals and reminders, simplifying the add-book flow, and making session completion more explicit.
Because Readit was not launched, I cannot claim that it changed long-term reading behavior. The next step would be to revise the prototype around the usability findings, run a second testing round, and eventually evaluate the experience over several weeks.
Next steps would involve deeper usability testing on the digital prototype with a wider demographic, and exploring the integration of community features to allow users to share their reading milestones. Ultimately, Readit proves that with the right structural support, building a healthy habit doesn’t have to feel like hard work.

