Hinge-Aware Dual-Screen Reader
A reader for dual-screen devices that lays books and long articles out as continuous two-page spreads around the hinge, advancing an entire spread with each turn.
On a dual-screen device, opening an EPUB, PDF, or long web article often produces one wide page split by a hinge. This reader treats the hinge as a book spine: after selecting a file, the user gets text reflowed across two facing pages, with margins and line lengths kept clear of the central gap. Each page turn advances a complete two-screen spread, so reading can finally feel continuous, like reading an open book.
Users can switch between side-by-side landscape pages and stacked portrait pages based on device orientation. Definitions, footnotes, and illustrations can stay pinned on the right while the main text remains on the left. When users annotate, notes are saved against the original page so they do not drift after reflow. Shared articles are first reduced to clean main text while retaining the original link and image credits, making it easy to return to the source after reading.
The initial release prioritizes reflowable EPUBs, well-structured PDFs, and web articles that work in reading mode. Scanned PDFs remain as original page images, while complex magazine layouts prompt users to switch to single-page viewing. Layout settings update in real time with font-size changes and rotation, making the second screen part of the reading surface rather than an extra blank display area.
Why now
An August 23, 2026 post in r/AynThor asked for a dual-screen reading app. Commenters suggested looking for Surface Duo solutions, but no existing answer was offered that actively paginates across both Thor screens. S1
Target user
Heavy readers who already own a Thor, Surface Duo, or similar dual-screen device. On commutes, before bed, or during long reading sessions, they unfold the device fully only to find that ordinary readers run text through the hinge. They often have local EPUBs, academic PDFs, and read-later articles, but do not want a separate app for every format. They need a dependable two-page rhythm and care about preserving their place and annotations after rotation.
Minimal entry point
On Android, use Jetpack WindowManager to read hinge position, occlusion bounds, and device posture, then divide the usable area into two independent pages. S2 Open EPUBs and well-structured PDFs with the Readium Kotlin Toolkit, whose Navigator already supports pagination, locations, and some highlighting functions. S3 Save reading progress as publication locations and store annotations separately with text context, rather than relying solely on reflowed coordinates. Initially limit web imports to semantically well-structured article pages, extracting body text, images, and source links through DOM parsing. Keep scanned PDFs as original-image two-page displays, without promising text reflow. Fall back to single-page viewing for complex magazines and malformed files, prioritizing reliable page turns, rotation, and reading-position recovery.
Punching above its weight
Early users are already looking for reading solutions in Thor, Surface Duo, and foldable-device communities. Release a test build with sample EPUB and PDF files so users can compare a standard hinge-spanning layout with one that avoids the hinge. Gather device models, orientation changes, and files that fail, then maintain a public compatibility list. Short videos should show only import, hinge-aware pagination, and full-spread page turns, so users can quickly tell whether their device is supported.
Competitors & gaps
- Amazon KindleGoogle
- Kindle has demonstrated book-like two-page reading on Surface Duo, showing that the dual-screen book form has an established reference point. S4 It works well for people already reading books in Kindle and lowers the learning curve for two-page page turns. Official material confirms Kindle support for Surface Duo, but does not say whether local EPUBs, standard PDFs, and web articles can enter one shared dual-screen workflow. It also does not demonstrate a general capability to calculate page widths dynamically around hinge boundaries. Keeping footnotes on one screen while the text stays in place on the other, and anchoring annotations across formats, are not the focus of that material. The opportunity is not another page-turn animation, but a way to accommodate users' existing open files and shared links. The layout must also recalculate reliably with rotation and device posture, with clear handling for scanned PDFs and complex layouts. If those differences are not plainly visible on devices such as Thor, users will likely stay with their current readers.
How it makes money
The free tier opens local files; a one-time Pro upgrade unlocks dual-screen layouts, annotation export, and web imports.
The case against
Hinge bounds and device posture may be reported inconsistently across dual-screen models, so adaptation work grows with every device. EPUBs must be repaginated after font-size changes; unstable page, footnote, or annotation locations would immediately interrupt resumed reading. PDFs vary widely in page dimensions, crop boxes, and two-page illustrations, making a single spread rule prone to cutting content incorrectly. Web extraction also faces login walls, dynamic loading, and missing images. Dual-screen device users are limited to begin with, and validating each model requires real hardware. If rotation, restoration, and page turns remain visibly unreliable on the first supported devices, readers will not entrust the app with their long-term library.