|
Stable EPUB annotations across devices: fixed layout or reflowable?
Hello everyone!
I'm a member of a software development team working on a cross-platform document and e-book reader.
We've been thinking about a particular challenge with EPUB reading, and I'd really appreciate hearing the opinions of experienced EPUB users here.
Our concern is keeping annotations accurately attached to their original content across different devices, especially when those annotations involve not just highlighted text, but also images, tables, diagrams, handwritten marks, and longer notes.
As we all know, EPUB is traditionally designed around reflowable content. This is wonderful for adjusting font sizes and reading comfortably on different screens.
However, reflowing can also make position-based graphical annotations more difficult to manage consistently across devices.
To address this, we've implemented a more stable, page-like rendering approach, while allowing users to read through the EPUB by scrolling continuously, somewhat like reading a PDF.
Our goal is to preserve the relationship between text, images, and their annotations as reliably as possible when moving between Windows PCs, tablets, and phones.
I'd love to hear your thoughts on a few questions:
1. Do you prefer continuous vertical scrolling or traditional page-by-page reading for EPUB books?
2. Would you find a stable-layout reading mode useful for technical books, textbooks, academic materials, or EPUBs with complex formatting?
3. If preserving the exact placement of diagrams and graphical annotations meant giving up some flexibility in font resizing or text reflow, would that be an acceptable trade-off?
4. Have you used any EPUB readers that handle cross-device graphical annotations particularly well, especially when switching between different screen sizes?
5. Would you prefer having both a traditional reflowable reading mode and a stable-layout annotation mode available?
We're particularly interested in learning about real-world reading habits and problems that users encounter.
We're still evaluating the best long-term approach, and constructive criticism would be very welcome.
Thank you for sharing your experience!
|