Publicado
Scrolling vs. Page Turns: How Apps Lay Out a Document
Every reading app makes a quiet decision before you've opened a single document: does the page turn, or does the text just keep going? The choice isn't cosmetic. It comes from centuries-old ideas about what a reading position should mean, and it still shapes how you read on your phone today.
What it is (one-paragraph answer)
Every document-reading app makes one layout decision before you read a word: does the screen scroll, or does the page turn? Continuous scroll treats a document as one long, unbroken surface — you move a viewport down it, with no hard stop between one section and the next. Page turning treats the same document as a stack of discrete units instead. You're always "on" a specific page, and moving forward is a jump, not a slide. Neither idea is new. Scrolling descends from the literal scroll — papyrus or parchment, rolled and unrolled by hand to reveal text. Pagination descends from the codex, the bound-page format that let a reader jump straight to a spot instead of winding through a continuous roll to find it. That's part of why the codex displaced the scroll for reference material in the first place.
Why it matters
The difference isn't just visual — it changes what a "reading position" actually means. A page number is a fixed, memorable landmark. Page 42 means the same thing every time you open the file, whether you're citing it, telling someone where you stopped, or picking the book back up next week. A scroll position, by contrast, is a pixel offset: precise, but not memorable, and meaningless to anyone but you. That's a real cost for reference reading. For the kind of reading you do start to finish, it's close to no cost at all.
Attention and scroll depth
There's a behavioral pattern worth knowing here too, independent of which layout an app uses. Eye-tracking research on scroll behavior finds that attention drops off sharply with depth — most viewing time now stays within the first few screenfuls of a scrolled page, no matter how long the page actually is. That's one reason a long PDF can feel harder to hold onto than a short one. It's also part of why reading a long PDF in pieces — rather than one continuous scroll — can make a dense document easier to actually finish.
Where you'll see it
Dedicated e-readers
Early e-ink readers didn't choose page turns for aesthetic reasons. The hardware forced it. E-ink displays refresh the whole screen slowly, so smooth, pixel-by-pixel scrolling wasn't practical — a page turn only needed one full refresh, not a continuous stream of them. The Sony Librie in 2004 and the Kindle in 2007 both leaned into paging because the display technology gave them no real alternative. That constraint shaped what a "normal" e-book reading experience felt like for years afterward, even once screens got faster.
How apps expose the choice today
Modern platforms build the choice directly into their document frameworks. Apple's PDFKit gives a PDF viewer four display modes: singlePage and twoUp turn discretely, while singlePageContinuous and twoUpContinuous scroll fluidly across page boundaries. An app picks per document, not just per platform — a reference PDF often defaults to continuous scroll for fast lookup, while something book-like defaults to discrete pages. Android apps make the same call between a swipe-per-page component and a plain scroll view. Different platform, same underlying question: should the reader's mental model be page-based or flow-based? The answer often depends on whether the document is reflowable text or a fixed layout to begin with.
How Margina handles it
Margina reads as a continuous document by default — closer to how you'd read a long article than how you'd navigate a paginated reference. Your position is saved precisely as you read, so opening a file again drops you back exactly where you stopped. No page number to remember, no account required to hold onto it. That fits how documents actually arrive in Margina: a chapter someone sent you, a PDF you AirDropped to yourself, a contract you need to get through once — not a reference you'll be citing by page. Highlights follow the same logic. They anchor to the content itself, not a page number, so they hold up even if the layout changes. If you want to try it, Margina is free for your first documents on the App Store and Google Play.
Frequently Asked Questions
Is scrolling or paginated reading better for comprehension?
Neither wins outright — it depends on the reading task. Pagination gives a document a durable, addressable landmark, which suits reference reading and anything you want to cite or return to precisely. Continuous scroll suits long, linear reading where momentum matters more than knowing exactly where you are. Attention drops off sharply past the first few screenfuls regardless of layout, so structure and length usually matter more than the scroll-vs-page choice alone.
Why did early e-readers use page turns instead of scrolling?
Mostly a hardware constraint. E-ink displays refresh the whole screen slowly, so smooth, continuous scrolling wasn't practical — a page turn only required one full refresh, not one per scrolled pixel. That constraint shaped reader expectations for years after the hardware improved.
Does Margina scroll or paginate?
Margina reads as a continuous document by default, closer to how you'd read a long article, with your position saved precisely so returning to a file drops you back exactly where you left off — no page number required, no account needed to remember it.
Conclusion
Scroll versus page turn isn't a right-or-wrong layout debate. It's a design choice about what a reading position should mean to you. A page number is a landmark; a scroll position is a flow. Both ideas are old, and both are still being chosen deliberately in the apps you use today — and the choice matters more, not less, as the same document keeps moving between formats, devices, and the people you send it to.