--- title: "Hinge-Aware Dual-Screen Reader" date: "2026-08-24" canonical: "https://raytally.com/en/ideas/2026-08-24-dual-screen-reading-apps/" generator: "RayTally · dev-prompt-v4" signal: query: "Dual screen reading apps?" observed_at: "2026-08-24T00:36:15.547Z" sources: - url: "https://www.reddit.com/r/AynThor/comments/1vw7pud/dual_screen_reading_apps/" boundary: "Published at 2026-08-23T00:00:00.000Z. Observed at 2026-08-24T00:36:15.547Z." - url: "https://developer.android.com/codelabs/android-window-manager-dual-screen-foldables" boundary: "No publication timestamp is present in the source record." - url: "https://github.com/readium/kotlin-toolkit" boundary: "No publication timestamp is present in the source record." - url: "https://blogs.windows.com/devices/2020/08/12/available-for-preorder-today-surface-duo-is-purpose-built-for-mobile-productivity/" boundary: "Published at 2020-08-12T00:00:00.000Z." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-08-24-dual-screen-reading-apps/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea 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. ## Product concept 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 (backed by facts) 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. ## Direction (model inference, not independently verified) 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. Open EPUBs and well-structured PDFs with the Readium Kotlin Toolkit, whose Navigator already supports pagination, locations, and some highlighting functions. 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. The strongest 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. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) 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 (model inference) - Amazon Kindle: Kindle has demonstrated book-like two-page reading on Surface Duo, showing that the dual-screen book form has an established reference point. 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 (model inference) The free tier opens local files; a one-time Pro upgrade unlocks dual-screen layouts, annotation export, and web imports. ## Source context Theme: Hinge-aware reading for dual-screen devices Trigger Reddit single-post demand observation: r/AynThor — Dual screen reading apps? This is one observation bounded by its publication and capture times. It is not evidence of market size or a broad trend and only explains “why now.” ## Sources - Dual screen reading apps? (https://www.reddit.com/r/AynThor/comments/1vw7pud/dual_screen_reading_apps/) - Support foldable and dual-screen devices with Jetpack WindowManager (https://developer.android.com/codelabs/android-window-manager-dual-screen-foldables) - Readium Kotlin Toolkit (https://github.com/readium/kotlin-toolkit) - Available for preorder today, Surface Duo is purpose-built for mobile productivity (https://blogs.windows.com/devices/2020/08/12/available-for-preorder-today-surface-duo-is-purpose-built-for-mobile-productivity/) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.