Readery - Redesigning Epub Reader on iOS

Designed for ease and focus, with intuitive annotations and reading settings that fit you.

I've started to notice small points of friction: a visually uninviting file list, limited note-taking options, and reading interactions that don't always feel intuitive.

At the same time, there are features I've never touched—like file-sharing options and cloud sync—which makes me question the app's overall structure and whether its priorities match how people actually use it.

Epub Reader is one of the apps I use most often on my phone. It's incredibly convenient for browsing books and articles on the go, and its feature set is refreshingly simple—almost minimalistic, in a good way. But that simplicity comes with trade-offs.

Screenshots of the EPUB Reader

Is it just me, or are others running into the same disconnect?

I want to understand whether other users share these frustrations or if they have entirely different needs I've overlooked. What tasks are they trying to accomplish when they open this app? Where does the current experience fall short—and more importantly, how could it better support their reading habits?

My goal isn't to overload the app with features but to design a smoother, more focused experience—one that feels just as lightweight but more thoughtful and adaptable to what users actually want.

Research

I turned to user reviews for insight since primary research wasn't allowed due to IRB restrictions. I sampled reviews directly from the App Store: 20 from EPUB Reader and 10 each from three other popular EPUB reader apps on iOS. In total, I reviewed feedback from 50 real-world users. By analyzing reviews, I hope to get a better picture of how people engage with EPUB apps and understand the user flow more broadly.

There were a few key questions guiding my review analysis:

What is the primary reason users open these apps?
While the app is called "EPUB Reader," it also supports PDFs and most text-based formats—many of which aren’t responsive or customizable in font size, typeface, or layout. So, what’s the point of supporting all these file types?
Do users take advantage of the file transfer features?
How are they getting their EPUB files—are they downloading them, transferring them between devices, or using third-party sources?
And perhaps most importantly: Which features do users love, and which ones consistently let them down?

Here are some results from
the qualitative coding method.

One interesting finding is that even within a single app, users can have completely opposite preferences when it comes to the reading experience. For example, two users who were using the same EPUB Reader's interface wrote,

“I'm only giving it 4 stars because you can't change the files to continuous scroll and I really don't like the page turning style.”

vs.

“I love how I turn the pages as a real book.”

The qualitative coding makes this clear—users, especially those of EPUB Reader, really want the ability to customize their reading mode. There's simply no single layout that works for everyone.

The same logic applies to readability features like font or line-height adjustment. Shaun Wallace and colleagues at Adobe conducted a reading-speed study with 352 participants and found that readers were, on average, 35% faster in their fastest font compared to their slowest. But that fastest font varied from person to person. In other words, the right visual setup makes a real difference—but what's "right" is highly individual. That's why customization is not just nice to have—it's essential.

Annotation features like note-taking, highlighting, and bookmarks received the most complaints, particularly in EPUB Reader. They lacked visibility and connection to the reading flow. Notes and highlights didn't feel integrated, making it hard for users to revisit what they marked or track their progress. Without visual cues or an easy way to return to the original text, the experience felt fragmented and less rewarding. One user shared,

“There are none of the bookmarks you left in the previous time, no notes, almost as though you've never opened the file. For this major annoyance, the app is getting deleted.”

Technical issues like screen freeze or missing content were also mentioned, but for the scope of this case study, I'll stay focused on the user experience side.

Building on these takeaways, I started mapping the flow and visualizing key screens.

The initial design reworks the structure of the original app and introduces a key new feature: the "Notebook" tab. This tab serves as a central space to collect all notes, highlights, and bookmarks. With it, users can easily trace their reading history, track annotation progress, and revisit meaningful moments from their books in a more streamlined way.

The reader view is also improved with more visual customization options, including multiple font choices, kerning adjustments, and text alignment controls. In addition, users can toggle default reading settings—such as book title, chapter name, and progress percentage—on or off, depending on their reading preferences.

Testing & Iteration

I approached testing through a simulated method since primary research is restricted. I created a paper prototype and walked through it by imagining myself as a few users who had left detailed reviews, following their desired flows to see how well the prototype aligned with their expectations. At the same time, two peer designers observed the process and provided feedback on the usability and logic of the design.

While testing, I realized the design leaned too heavily toward file & library management and drifted away from its core purpose—reading. Features like renaming files or changing covers are one-time setup actions and shouldn’t interfere with the reading flow.

This iteration focuses on reducing cognitive overload and keeping the interface centered around reading. By prioritizing high-frequency actions and applying progressive disclosure, the design helps users stay oriented and return to their books with minimal friction.

1. Short cut to last read

Added a shortcut to continue the last-read book from the home screen for quicker access.

2. Reorganized the tap-and-hold menu

Placing reading-related actions like "Continue Reading" and "View Notes" at the top while moving setup tasks to the book's settings page.

3. Streamlined the reading entry point

Clicking on a book cover now takes users directly to the reader if there's reading history; otherwise, it opens the book detail page.

4. Refined the file import flow

Allowing renaming and cover selection during upload, reducing the need for post-import edits.

5. Introduced a search feature and
alphabet scrollbar

When sorting books A–Z, helping users quickly locate titles in larger libraries.

Here’s a prototype where you can get a feel for the reading experience.

Visions

The curiosity and drive to seek knowledge live in everyone—so the reading experience should be accessible to everyone, too. In my vision, the app should be inclusive of users with visual or physical impairments, ADHD, dyslexia, and other diverse needs. Only one out of four apps mentioned in this research offered a text-to-speech (TTS) feature with voice customization, yet nearly 30% of its reviews praised it.

Features like TTS, auto-scroll, voice commands, and bionic reading aren’t just beneficial for users with specific impairments—they can improve the experience for all users, especially in certain contexts like commuting, multitasking, or screen fatigue. In the end, that’s what this whole redesign is about: making reading easier, more comfortable, and more accessible for everyone.