Breakdowns: Reading. How the best reading products get out of the way.

Warm-up: what do you already notice?

You read on screens for hours a day, so you already hold strong opinions about reading products. Most of them are unspoken. This guide makes them speakable. Before we start, try two questions. Don't look anything up; the point is to find out what your eye already catches.

A reading product is great when it gives the text the best possible surface, then removes itself, and only comes back when you need to find, mark, move or keep something.

Most software wants your attention. A reading product wants you to give your attention to something else: the book, the article, the essay. That inversion is why reading products are such a good school for designers. Every pixel of chrome, every badge, every recommendation competes with the thing the person came for. The best ones are almost invisible, and the work behind that invisibility is enormous.

Oliver Reichenstein of iA put it in one line in 2006: web design is 95% typography. For a reading product the number is closer to 100% while you are reading, and then drops sharply in the other moments: opening the app, finding a book, looking up a word, coming back on your phone. A useful scorecard has to cover both: the surface (how the text looks) and the system (everything around it).

The ten criteria

Here is the lens we will use for the whole guide. Each criterion is scored 0 to 3. Zero means absent or harmful, one means present but weak, two means good, three means best in class: other products should copy it.

1 · Surface typography

Typeface designed for long reading at screen resolution, sensible size, a measure (line length) of roughly 45 to 75 characters, leading around 1.4 to 1.6, real hyphenation if text is justified, proper quotes and dashes, no widows of one word on a page. See Typography for the underlying rules.

2 · Defaults

How good it is untouched. Most people never open settings, so the default is the product.

3 · Controls

Can you change what actually matters (size, theme, spacing, margins, face) in one or two taps, with a live preview, without breaking the layout?

4 · Navigation & progress

Do you know where you are and how much is left, in units that mean something to you? Can you jump to a chapter and jump back?

5 · Annotation

Highlighting and notes that are quick to make, easy to find again, and travel with you.

6 · Sync & continuity

Your place, highlights and settings follow you across devices and even formats (text to audio).

7 · Library & collection

Finding, sorting, grouping and pruning what you own or saved. A library that grows past 500 items without collapsing.

8 · Discovery vs distraction

Helping you find the next thing to read without pulling you out of the current one.

9 · Accessibility

Wide size range, high contrast options, dyslexia-friendly options, screen reader and text-to-speech support, one-handed use. See Accessible & Inclusive.

10 · Ownership & export

Open formats, DRM-free where possible, highlights and saves you can export in a usable format. The test: if the company died tomorrow, what would you lose?

Why ten, and why 0 to 3

Ten is enough to separate products and small enough to finish in a single sitting. A four-point scale forces a decision: there is no neutral middle to hide in. If you are tempted to give a 2, ask "would I tell another designer to copy this?" If yes, it's a 3. If you'd say "it's fine", it's a 2. If you'd say "it's there, but…", it's a 1.

Scores are not the point. The observations behind them are. A score of 1 on Navigation is useless; "the progress bar shows percentage only, and I can't tell how long the chapter is" is a design insight you can act on.

In the wild

• KindleAmazon, 2007–
  The strongest system in reading: sync, dictionary, notes across every device. Weakest on ownership and on keeping the store out of the library. Great systems can carry an average surface for years.
• Standard EbooksVolunteer project, 2017–
  Ebooks typeset with care to a public style manual, free and DRM-free. No app, no sync: they rely on your reader for that. A great surface with no system of its own.
• Readwise ReaderReadwise, 2022–
  Scores high on annotation, library and export; the surface is good but dense with power features. Power can be a 3 and a cost at the same time.

A reading product is not a screen; it is a session with six moments, and each moment has a different design job.

When you take apart a reading app, the temptation is to look at the reading page and stop. But people don't experience a page; they experience a session that starts before the page and ends after it. Breaking the session into moments shows you where products actually differ. Two e-readers with identical text rendering can feel completely different because one opens straight to your book and the other opens to a store.

The protocol

1. Cold open. Kill the app. Open it. Count the taps and seconds until you are reading the sentence you left. Note everything on screen in between.
2. Settle. Change one thing (size or theme). Count taps. Is the change previewed live? Does your place on the page survive the reflow?
3. Immerse for ten minutes. Don't analyse. Afterward, write what you remember of the interface. If you remember nothing, that's a compliment.
4. Mark. Highlight a passage, add a note, look up a word. Then try to find that highlight again from the library.
5. Leave mid-chapter. Close it while partway through a page.
6. Return elsewhere. Open the same item on a second device (or the web). Where does it put you? Does it ask?

In the wild

• Kindle e-readersAmazon
  The home screen has gone back and forth over the years between a plain list of your books and a mix of your library with store recommendations. The Arrive moment is where business goals push hardest into reading.
• Apple BooksApple, 2010–
  Opens to a Home tab with "Continue" at the top: the book you were reading is the first thing you see. Put the most likely next action first.
• Reader modesSafari, Firefox, Edge
  Exist purely to fix the Immerse moment on web pages that fail it. When a whole category of tool exists to remove your interface, your interface is too loud.

When the first Kindle shipped in November 2007 it was an odd beige slab with a keyboard. What made it matter was the wireless delivery: you bought a book and it appeared in about a minute, with no computer involved. Everything Kindle has done since builds on that idea of the book as a live, connected object. Your reading position syncs (Whispersync). Your highlights live in the cloud. The dictionary is built in. The text knows what's in it (X-Ray). Each of these is a design decision with a cost, and Kindle is the best place to study those costs because it has been making them for almost twenty years.

1. Typesetting that respects the book. In 2015 Amazon introduced Bookerly, a typeface it commissioned from Dalton Maag for reading on its screens, together with a new typesetting engine (marketed as enhanced typesetting) that improved spacing, kerning and later hyphenation, and added drop caps. Before that, justified Kindle text often had visible "rivers" of white space because there was no hyphenation. The cost: older books and badly made files don't benefit equally, so quality varies from book to book.
2. Justified text with hyphenation by default. Print books are justified, so Kindle matches the expectation. Justification only works well with hyphenation and a long enough line; at large font sizes on a small screen, gaps return. Kindle lets you switch to left-aligned (ragged right), which is the safer choice at big sizes.
3. Popular Highlights. Since around 2010 Kindle has aggregated highlights across readers and shows passages many people marked. It's a fascinating social signal, and it raised a long-running privacy question: your highlights are data Amazon collects. It can also steer your attention ("I should notice this"), which some readers find spoils the book. You can turn it off. The cost of a default here is ethical as much as visual. See Honest & Calm.
4. Reading aids at the word level. Tap a word for the dictionary and Wikipedia. Word Wise (2014) puts short definitions above harder words, with a slider for how many words get hints. Vocabulary Builder collects every word you looked up into flashcards. Together they turn a lookup into learning, without leaving the page.
5. Time left, not just pages. Kindle learns your reading speed and can show "time left in chapter" or "time left in book". This answers the question readers actually ask at 11pm ("can I finish this chapter before sleep?"). The estimate needs a few pages of data before it's good.
6. Locations, then pages. Reflowable text has no fixed pages, so Kindle invented locations: fixed positions in the file that don't change with font size. They are stable for citations and sync, but meaningless to humans. Many books now map to real print page numbers, shown when available. Percentage is always there.
7. X-Ray. Introduced in 2011, X-Ray shows the characters, places and terms in a book and where they appear. It solves "who is this again?" in long novels without spoilers past your position. It needs per-book data, so not every book has it.
8. Whispersync and Page Flip. Whispersync keeps your furthest page, bookmarks and notes in sync across devices, and asks before jumping you forward. Page Flip (2016) lets you peek at other pages in a thumbnail view while your place stays pinned, the digital version of keeping a finger in the book.

Trade-offs and criticisms

• The store in the library. Kindle's home screen and lock screen (on ad-supported models) carry recommendations and offers. It pays for cheaper hardware, but it puts the store into the Arrive moment of every session.
• Closed format. Kindle books are generally tied to Amazon's apps and devices. Amazon has added EPUB support to Send to Kindle (converted on the way in), but the purchased library stays inside the ecosystem.
• Highlight export is limited. Notes and highlights are viewable on the web and some can be exported, often with publisher limits on how much. Tools like Readwise exist partly to fill that gap.

In the wild

• Kindle PaperwhiteAmazon, 2012–
  Front-lit e-ink made the Kindle usable in bed without a lamp, and later models added warm light. Hardware decisions are reading-design decisions: light colour affects how long people read at night.
• Kindle Vocabulary BuilderAmazon
  Collects words you looked up, with the sentence they came from, as flashcards. Context is the memory hook; keep the sentence.
• Kindle NotebookAmazon
  A per-book list of highlights and notes, filterable, linking back to the passage. Annotation is only useful if you can find it again.

If Kindle is the system, Kobo is the toolbox. Its e-readers have long given readers controls that other makers hide or skip: font weight and sharpness sliders, fine margin and line spacing steps, justification options, and the ability to load your own fonts. It reads EPUB, the open standard most of the publishing world uses, so a DRM-free book from anywhere just works. It has built-in library lending through OverDrive in many regions. And for years its devices had Pocket built in, so web articles you saved appeared next to your books; when Pocket closed in 2025, Kobo moved that role to Instapaper in a software update later that year.

1. A half-sheet, not a settings page. Kobo's type settings slide up over the bottom of the page. The text stays visible, so you see the change as you make it. This is the single most important pattern for reading controls.
2. More steps, finer steps. Size, line spacing and margins each have many increments. A reader with low vision or a love of tight text can both get exactly what they want.
3. Weight and sharpness. E-ink renders thin fonts faintly, especially on older screens. Kobo's Advanced sliders let you thicken strokes and sharpen edges. It solves a real hardware problem with a typographic control rather than a hardware fix.
4. Buttons for one-handed reading. The Kobo Libra line (2019 onward) has physical page-turn buttons on a wide side grip, and the device flips its layout for left or right hand. Tapping a screen with a thumb stretched across it is a tiring, error-prone gesture; a button under the thumb isn't.
5. Open by default. EPUB support means DRM-free books from Standard Ebooks, independent authors or publishers like Tor work without conversion. Kobo also lets you sideload fonts. Openness is a feature for the reader and a moat-reducer for the company.

Trade-offs

Many settings means many combinations, and some of them are ugly. Kobo accepts that cost for its audience of keen readers. Its defaults are good, which is what keeps the controls from becoming a burden. The other trade-off is ecosystem: Kobo's store is smaller in some markets, and its sync between devices and apps has historically been less seamless than Kindle's.

In the wild

• Kobo Libra seriesRakuten Kobo, 2019–
  Asymmetric body with page buttons; screen rotates for either hand. Design for how the device is held for an hour, not how it looks in a photo.
• Kobo + OverDriveRakuten Kobo
  Borrow library ebooks directly on the device in supported regions. Integrate the source people already use, not just your store.
• Kobo + Instapaper2025
  Replaced the Pocket integration after Pocket closed. Integrations are dependencies; design so one can be swapped.

iBooks launched with the iPad in 2010 and its demo was unforgettable: a wooden bookshelf, and pages that curled under your finger, following it in real time, with the next page showing through. It taught a whole generation that a tablet could hold books. Over the next decade the wood went away (the iOS 7 redesign of 2013 flattened nearly everything), the app was renamed Apple Books in 2018 with a "Reading Now" home, reading goals arrived in 2019, and in 2022 the reading view was rebuilt around a small set of themes. Following that arc is a lesson in when metaphors help and when they get in the way.

1. The page curl as an explanation. In 2010, nobody knew how to read on a tablet. A page that bent under your finger made the gesture self-evident: grab the corner, pull. It was a teaching device as much as an animation. See Motion & Feel for why direct manipulation feels right.
2. Dropping the curl as the default. In the 2022 redesign the default turn became a quicker slide; after complaints, the curl came back as an option. Once a gesture is learned, a heavy animation costs more (time, visual noise) than it teaches. Keeping it optional respects people who love it.
3. Continue first. The home tab puts the current book (and audiobook) at the top with progress. The Arrive moment is one tap.
4. Themes as presets. Instead of asking readers to tune five settings, the 2022 reading view offers a handful of named themes that set face, weight, spacing and background together, each customisable. A preset is a decision made on the reader's behalf that they can still undo. Good presets carry a design opinion; that's the point.
5. Scrolling view. Apple Books offers a continuous vertical scroll as an alternative to pages. Some people (and some content, like technical books) read better in scroll; pages give stronger landmarks ("it was near the top of a left page").
6. Reading goals. A daily minutes target (5 minutes by default, changeable) and a streak. Small default, real habit. Goals are a calm motivator only if they are easy to switch off and don't nag. See Honest & Calm.
7. Books and audiobooks in one library. The same app holds both, with a shared "Continue" row. Listening is treated as reading, not a separate product.

In the wild

• iBooks page curlApple, 2010
  Followed your finger frame by frame, with text visible on the back of the page. Direct manipulation teaches a gesture faster than any tutorial.
• Apple Books reading goalsApple, 2019
  Daily minutes target and streaks, with the goal adjustable from the home screen. Make the habit visible, keep the pressure low.
• Play BooksGoogle
  Also offers a "flowing text" and "original pages" toggle for scanned or fixed-layout books. Let the content's nature pick the view.

Borrowing an ebook from a library is a strange transaction. Libraries license digital copies, often one reader at a time, for a limited number of loans or months. So there are waitlists for ebooks, which surprises people. The older OverDrive app exposed much of this machinery. Libby, launched in 2017, kept the same back end and redesigned the experience around one person with a library card and a phone. OverDrive later retired its older app in favour of Libby. Its users range from teenagers to readers in their 80s, so it's a valuable study in designing for everyone.

1. Plain words for a complicated system. "Loans", "Holds", "Due in 9 days", "You're #4 in line". Libby's copy is warm and a little playful in its onboarding, but on the shelf it's plain and specific. Older readers don't need to learn library software jargon.
2. Honest waits. A hold shows your place in line, how many copies the library owns and an estimated wait. Uncertainty is shown, not hidden. People tolerate waiting far better when they can see why.
3. Deliver later. If a hold comes in when you're busy, you can let the next person go ahead while keeping your place near the front. It turns a rigid queue into a polite one. It's a lovely example of designing the edge case.
4. Tags instead of folders. You can tag any book you see, Libby adds a few automatic "smart" tags for things like books you have sampled or borrowed, and tags work across your libraries and searches. A flexible structure with almost no learning cost.
5. Read in Libby, or send elsewhere. Libby has its own reader and audio player. In the US, many ebooks can also be sent to a Kindle. Libby meets readers on the device they already love.

In the wild

• Libby onboardingOverDrive, 2017–
  Walks you through finding your library and adding a card in a friendly, conversational sequence. Onboarding can be a conversation when the setup really has steps.
• HooplaMidwest Tape
  Another library app, built on an "instant borrow, no waitlist" model with monthly limits. Business model shapes the core screen: no queue means no hold UI.
• Kindle + LibbyUS
  "Read with Kindle" hands the loan to Amazon's ecosystem. Let readers choose their surface.

Project Gutenberg is the oldest digital library: Michael Hart typed the US Declaration of Independence into a mainframe in 1971 and shared it. Since then volunteers have transcribed tens of thousands of public-domain books. Its focus has always been access: get the text out, free, in simple formats. Standard Ebooks, a newer volunteer project, takes those transcriptions (and scans) and produces carefully typeset, consistently formatted ebooks with modern conventions, semantic markup and a public Manual of Style that explains every rule. Compare the same novel from both and you'll see what "typography is invisible" really means.

1. Write the rules down. Standard Ebooks publishes a Manual of Style covering punctuation, typography, semantics, metadata and file structure. Every volunteer follows the same rules, so every book feels like part of one edition. A style manual is a design system for prose.
2. Semantic markup first. Text is marked up for what it is (a letter, a poem, a quotation, an abbreviation), not how it looks. That makes books work across readers, with screen readers, and when styles change later.
3. Modernised, consistently. Some archaic spellings are updated according to documented rules, so a reader isn't tripped by "to-day" or inconsistent hyphenation, while the author's words are kept. The rules say what is changed and what is left alone.
4. Covers from public-domain art. Each book gets a cover using a public-domain painting with a consistent title treatment. A library of them looks like a collection, not a pile.
5. Free, DRM-free, multiple formats. EPUB, Kindle-compatible files and others. The books scorecard a full 3 on Ownership.
6. Gutenberg's choice: access over polish. Project Gutenberg's plain-text-first approach meant texts survived decades of format changes. Its HTML and EPUB editions have improved a lot over the years, but its core value is breadth and permanence. Both choices are right for their goals.

In the wild

• Standard Ebooks Manual of Stylestandardebooks.org
  Public, detailed, versioned rules for every book. Write the decisions down once; let many hands produce one voice.
• Project Gutenberg1971–
  Decades of free texts in durable formats. Permanence and access are design goals too.
• SmartyPantsJohn Gruber, 2002
  A small tool that converts straight quotes and dashes to typographic ones, used in many publishing systems. Automate typography where you can.

Part two recap: connect the ideas

Five book products, five philosophies: Kindle builds the system, Kobo hands over the controls, Apple Books makes opinionated presets, Libby translates machinery into plain language, and Standard Ebooks treats typography as a public craft. Before moving on, check the links back to earlier guides.

Marco Arment built Instapaper in 2008 as a side project: a "Read Later" bookmarklet that saved a page to a list, and a way to read that list later, especially offline on the then-new iPhone. The key insight was splitting reading into two moments that happen at different times: finding (at your desk, busy) and reading (on the train, in bed, unhurried). The app's text view stripped each article down to words and set them beautifully. Arment charged for the app instead of filling it with ads, and that business choice kept the product calm. He sold a majority of it to Betaworks in 2013; Pinterest bought it in 2016; since 2018 it has been run independently.

1. One button, no decisions. Saving asks nothing: no folder, no tag, no note. The moment of finding is the busiest moment, so the cost there must be near zero. Organisation can happen later, if ever.
2. A list that tells you length. Each item shows the source and an estimate of reading time. Length is the main thing you need to pick what to read now.
3. Text view as the product. The extraction (getting the article out of the page) and the typesetting of the result are the core. Instapaper offered a small set of good fonts, size, line spacing, margins and themes, in a compact settings popover over the text.
4. Paid, therefore calm. Arment's model was simple: people pay, so the product serves readers rather than advertisers. Instapaper later moved to a free tier plus Premium (with features like full-text search and unlimited notes). The business decision shows up on every screen as an absence of ads and engagement tricks.
5. Speed Reading. Instapaper added a speed reading mode that flashes one word at a time at a chosen pace. It's a fascinating experiment and a useful lesson: it raises speed by removing the eye's ability to go back, which hurts comprehension for many texts. A feature can be clever and still be a niche tool.

In the wild

• Instapaper on Kobo2025
  After Pocket closed, Kobo devices integrated Instapaper so saved articles appear next to books. A simple, stable product becomes the safe partner.
• Things Quick EntryCultured Code
  Capture a task from anywhere with one shortcut, sort it later. Same capture/process split, different domain.
• Safari Reading ListApple, 2011
  Built read-later into the browser, with offline saving. Once a pattern is proven, platforms absorb it; independents must go deeper.

Pocket started as Read It Later, a Firefox extension, in 2007. In 2012 it was renamed Pocket and relaunched as a free app with a cleaner design. It grew huge by being everywhere: browser extensions, a share-sheet action in thousands of apps, an email address you could send links to, and built-in integrations (Kobo e-readers among them). Mozilla bought it in 2017 and put Pocket recommendations into the Firefox new tab page. In May 2025 Mozilla announced it would shut Pocket down; the service closed in July 2025, with a window to export data that ran into October. This chapter is half breakdown, half obituary, because the ending is the lesson.

1. Free and everywhere. Becoming free in 2012 and integrating with as many apps as possible made Pocket the default "save" target for a decade. Distribution was the design.
2. Discovery built in. Pocket used what people saved to surface popular and recommended articles, later inside Firefox. This helped people find good reading, and blurred the line between "my list" and "a feed".
3. Tags, highlights, listen. Pocket added tags, highlights and text-to-speech. Useful, but each made the data more valuable to the user, and therefore made export more important.
4. The ending. Mozilla gave notice, kept export open for months after the service stopped, and pointed people at alternatives. That's a decent ending as endings go. But many people discovered that their tags, highlights and years of saved reading lived in a format other apps imported only partly.

In the wild

• Google ReaderGoogle, 2005–2013
  Its 2013 shutdown pushed millions to Feedly and others; Google Takeout let people export subscriptions as OPML. An open export format (OPML) made the migration possible.
• Pocket shutdownMozilla, 2025
  Announced in May, service ended in July, with an export window into October. Notice and export are the minimum ethical ending.
• ObsidianDynalist Inc., 2020–
  Stores notes as plain Markdown files in your folders. The strongest export is no lock-in at all.

Readwise began as a service that pulled your Kindle highlights (and later highlights from many apps) into one place and resurfaced a few each day by email or in the app: a Daily Review. Reader, launched in public beta in 2022, is the reading app built to feed that system. Its premise is that the boundaries between "articles", "PDFs", "newsletters" and "feeds" are artificial. To a reader they're all text to triage, read, mark and remember. Reader is dense and powerful, and it is a useful counterpoint to the minimal products in this guide: power done thoughtfully.

1. Library vs Feed. Things you chose to save go to the Library; things that arrive by subscription (RSS, newsletters) go to the Feed. This draws a firm line between "I decided this" and "this arrived", which keeps the Library from flooding.
2. Triage states, not folders. Inbox, Later, Shortlist, Archive. Each item is in exactly one state, and moving between them is one key. It's email triage applied to reading: decide quickly, read deliberately.
3. Every format, one toolset. Highlighting a PDF, an EPUB, a web article or a video transcript works the same way, and all highlights flow to the same place. One mental model across formats.
4. Keyboard first, mouse welcome. Nearly every action has a shortcut, with a command palette to find them. Power users can triage dozens of items a minute; newcomers can still click. See Breakdowns: Software for the same idea in Linear and Superhuman.
5. AI at the side. Ghostreader offers summaries, definitions, simplification and questions about the document, using a language model. It lives in the side panel and in explicit commands, not as text injected into what you're reading. See Designing with AI.
6. Review as the point. Readwise's Daily Review resurfaces a handful of past highlights each day, with spaced repetition options for ones you want to memorise. Reading isn't finished when you close the article; it's finished when you remember it.

In the wild

• Readwise Daily ReviewReadwise
  A short daily session of past highlights, with options to master, tag or discard. A small daily ritual beats a big archive.
• Superhuman2017–
  Email triage with keyboard shortcuts and a command palette. Reader borrows email's best interaction pattern for reading.
• AnkiDamien Elmes, 2006–
  The open-source spaced repetition app. Spaced review is a mechanism, not a feature; it can live inside any product with saved items.

The read-later category got a second wind in the early 2020s. Two products are worth studying side by side. Matter, an iOS-first app, built its identity around natural-sounding text-to-speech: you can listen to a saved article with the current word highlighted in the text, switch between reading and listening without losing your place, and highlight while listening. Omnivore was a free, open-source read-later app with highlights, labels, newsletters, PDFs and plugins for note apps like Obsidian. In late 2024 the Omnivore team joined ElevenLabs and the hosted service was shut down within weeks, with a short window to export. Its code remained available, but most users don't self-host.

1. One position for two modes. Reading and listening share a single place in the text. Stop listening on the street, keep reading at home, from the same sentence.
2. Follow-along highlighting. Showing the spoken word in the text helps people who want to read and listen at once (a big help for some readers with dyslexia and for language learners), and makes it easy to drop back into reading.
3. Highlight while listening. A tap marks the passage just spoken. Annotation shouldn't require eyes on the screen.
4. Omnivore's openness. Open source meant transparency, self-hosting and community plugins. It didn't guarantee continuity of the hosted service people actually used. Openness of code and continuity of service are different promises.

In the wild

• Matterearly 2020s–
  Text-to-speech with word-level follow-along and highlighting while listening. Listening is reading by other means.
• Omnivore2022–2024
  Free and open-source; hosted service closed in late 2024 after the team joined ElevenLabs. Users experience the service, not the licence.
• Podcast apps (Overcast)Marco Arment, 2014–
  Smart Speed shortens silences without making voices sound sped up. Audio controls can respect the content rather than just speed it up.

In 2009 the design studio Arc90 released Readability, a bookmarklet that turned a cluttered page into clean text with good typography. It used heuristics: score each block of the page by how much text it has, how many commas, how few links, and what its class names suggest ("article", "content" up; "comment", "sidebar", "ad" down). Apple built Safari Reader (2010) using Readability's open-source code. Mozilla maintains its own Readability.js library, which powers Firefox Reader View. Today every major browser has some reader mode. The interesting part for a designer is the mechanism: your page is being scored by a machine trying to find your article. Semantic HTML helps it, and helps everyone.

1. Guess, then let the user fix it. Extraction is heuristic, so it will sometimes be wrong. The reader mode button only appears when the browser thinks a page is article-like, and the original is always one click away.
2. Typography handed to the reader. Reader modes offer a few faces, sizes, widths and themes. They assume the reader knows best about their own eyes, a reversal of the usual web, where the publisher decides.
3. A narrow column by default. Reader modes set a comfortable measure no matter how wide the window is. This one decision fixes the most common reading problem on desktop sites.
4. Listen and translate. Many reader modes add read-aloud, and some add translation or line focus (Microsoft Edge's Immersive Reader is the richest example). Once the text is clean, other tools can work on it.

In the wild

• ReadabilityArc90, 2009
  The bookmarklet that started it; its heuristic approach lives on in many tools. A small open tool can set a standard for a whole platform.
• Safari ReaderApple, 2010–
  Appears in the address bar when a page looks like an article; can be set to open automatically per site. Per-site memory turns a fix into a preference.
• Edge Immersive ReaderMicrosoft
  Adds line focus, syllable breaks, parts of speech and picture dictionary. Reading support for learners and dyslexic readers is a design space of its own.

Part three recap: connect the ideas

Instapaper split capture from reading. Pocket made capture universal and taught the price of no exit. Readwise Reader made triage and review the core. Matter joined listening to reading. Reader modes proved that the clean text view is what people want from the web.

RSS lets any site publish a feed of new posts, and lets you read all of them in one app, in order, without an algorithm. It's the original calm technology for reading the web, and it survived the 2013 shutdown of Google Reader, which pushed millions of users to services like Feedly. The four products here show the main design choices. NetNewsWire is a free, open-source, very Mac-like app: three panes, unread counts, keyboard shortcuts, nothing extra. Feedbin is a paid web service with a clean reader and a private email address for newsletters. Feedly grew into a discovery and research platform, now with AI features. Reeder, by Silvio Rizzi, was rebuilt in 2023 around a single timeline with no unread counts, keeping the older design available as Reeder Classic. (Breakdowns: Software covers Reeder's interaction design in more depth.)

1. Counts as an option, not an accusation. Unread counts are honest for low-volume feeds and corrosive for high-volume ones. Good readers let you hide counts, per feed or globally, and show a small dot instead of a red number.
2. Timeline with memory (Reeder, 2023). One stream, newest at the top, with the app remembering your position. It reframes RSS from "inbox zero" to "what's happening", much closer to how people actually read feeds.
3. Platform fit (NetNewsWire). Standard Mac controls, standard keyboard shortcuts, standard three panes. People who know Mail know NetNewsWire. Brent Simmons has written about building it to be fast and stable rather than feature-rich.
4. Newsletters as feeds (Feedbin). A private email address that turns newsletters into feed items. It rescues reading from the inbox, where it competes with work.
5. Open source as continuity (NetNewsWire). Free and open source, with sync through several services, it's unlikely to disappear in a way that strands users. Compare Omnivore in chapter 11: open code helps most when the app runs locally.

In the wild

• NetNewsWire 5+Brent Simmons, 2019–
  Free, open source, fast, native. Restraint and platform fit are features.
• Reeder (2023)Silvio Rizzi
  Unified timeline across feeds and social sources, no unread counts; the previous app continued as Reeder Classic. You can change a product's philosophy without abandoning existing users.
• FeedbinBen Ubois, 2013–
  Paid, clean, with newsletter email addresses. A small paid service can stay calm and sustainable.
• Feedly2008–
  Absorbed many Google Reader users in 2013, later added AI-assisted filtering for professionals. Different audiences (casual readers vs analysts) justify different densities.

Medium launched in 2012 when most blogs looked like templates from 2005. Every Medium post got the same thing: a generous serif column, big images, a clean title, and nothing in the margins. Writers didn't have to design anything, and readers got a consistent, good page. Medium added an estimated reading time to every post. Its help documentation describes it as based on an average adult reading speed of about 265 words per minute, with extra time for images. Readers could highlight text and see the passages others highlighted most ("Top highlight"). Substack, founded in 2017, made the newsletter the primary format: posts arrive by email and also live on a web page and, later, in Substack's own reading app.

1. One layout for everyone. Writers can't change fonts or colours. This removes bad design choices from the platform and makes every post feel like part of one publication. The cost is personal expression; Substack and others later offered more customisation.
2. Reading time in the byline. "7 min read" answers "should I start this now?" before the first sentence. It also changed writing: authors and editors began thinking in read-minutes, and Medium at times used reading time in how it measured engagement.
3. Highlights as social reading. Highlighting is private by default, but aggregated highlights appear to others. It turns a solo act into a quiet signal, with the same steering risk as Kindle's Popular Highlights.
4. Inline responses and notes. Medium experimented with notes in the margin next to paragraphs and later with responses as full posts. Commenting next to the text is precise; it can also clutter the column.
5. Substack: the inbox as the reading surface. Email arrives reliably and is owned by the reader. But the inbox is a work tool, full of competing demands. Substack's app and web reader try to give newsletters a calmer home.
6. Paywalls and prompts. Both platforms show subscribe prompts and paywalls. Where they sit (top, mid-article, end) is a reading-design decision with a business motive. Mid-article prompts break immersion most.

In the wild

• Medium reading timeMedium
  Based on about 265 words per minute plus an allowance for images, per its help documentation. Show the model, round the output.
• Substack appSubstack
  A dedicated reading app for subscriptions, separate from email. Move reading out of work spaces when you can.
• GhostGhost Foundation, 2013–
  Open-source publishing with themes focused on readable article pages and member newsletters. Ownership for writers is the same principle as export for readers.

For over a decade, Wikipedia's desktop skin (Vector, from 2010) stretched text across the full width of the browser window. On a big monitor that meant lines of 150 characters or more. Vector 2022, developed over several years and rolled out first on a number of smaller-language Wikipedias, limited the content width, added a sticky header with the article title and search, moved the table of contents into a sidebar that stays visible as you scroll, and collapsed the main menu. It became the default on English Wikipedia in January 2023, after a long and divided community discussion. Logged-in users can switch back to the old skin, and anyone can toggle full width.

1. Limited width. A comfortable measure makes long reading less tiring. On wide monitors the old design was far outside the range typographers recommend. The cost: empty space on the sides, which some readers saw as wasted, and tables and images that had more room before. A full-width toggle keeps the choice.
2. Sticky header. Title, search and tools stay reachable while scrolling a long article. On a reference site, search is a primary action, often used mid-article.
3. Table of contents in a sidebar. Long articles become navigable: you see where you are and can jump without scrolling to the top. Wayfinding, the reference-reading equivalent of "time left in chapter".
4. Collapsed main menu. Links most readers never use moved behind a menu button, which saved space and reduced noise, and annoyed editors who used them daily.
5. Gradual rollout, with research. The Foundation deployed to smaller wikis first, tested features, and published findings and documentation. The English Wikipedia discussion still showed many editors opposed. The lesson: research can tell you what helps most readers; it doesn't remove the cost to experts whose habits change.

In the wild

• Vector 2022Wikimedia, 2023 on English Wikipedia
  Limited width, sticky header, TOC sidebar, full-width toggle. Readability research and expert habits can pull in opposite directions; give both a path.
• MDN Web DocsMozilla
  Sidebar navigation plus an "In this article" outline that tracks scroll. Two levels of wayfinding for long technical pages.
• Stripe DocsStripe
  Narrow prose column with code alongside on wide screens. Use spare width for related content, not longer lines.

Is listening to a book "reading" it? For a designer the useful answer is: it's the same book, in a different form, for a different moment. Amazon made this concrete in 2012 with Whispersync for Voice: if you own both the Kindle book and the matching Audible audiobook, your position syncs between them. Immersion Reading goes further and plays the narration while highlighting the text as it's read, on supported Kindle apps and Fire tablets. Apple Books keeps audiobooks in the same library as ebooks. Speechify, a text-to-speech app, reads any text (web pages, PDFs, scans) aloud with follow-along highlighting; its founder has spoken about growing up with dyslexia, and the product grew from that need.

1. Align audio to text. The underlying work is alignment: knowing which sentence is spoken at which second. Every feature (sync, follow-along, highlight while listening) comes from that one map.
2. Confirm, don't jump. Cross-format sync suggests the furthest position and asks, just like device sync on Kindle.
3. Controls for hands-busy moments. Big skip-back (15 or 30 seconds), sleep timers, speed in small steps, lock-screen and headphone controls. Listening usually happens while doing something else.
4. Text as support for the voice. Follow-along highlighting helps people with dyslexia, language learners and anyone who wants to read faster with audio pacing. It's an accessibility feature that many people simply enjoy.
5. Bookmarks by time and text. An audio bookmark should show the sentence, not only "2:14:07".

In the wild

• Whispersync for VoiceAmazon, 2012
  Switch between Kindle book and Audible narration at the same place. Continuity across forms, not just devices.
• Immersion ReadingAmazon
  Narration plus text highlighting on supported apps and devices. Two senses at once can help comprehension and focus.
• YouTube transcriptsGoogle
  Click any line of the transcript to jump the video there. The same alignment idea, applied to video.

Some of the best reading products aren't apps at all. Gwern.net is a personal site of long, heavily referenced essays. Its design (developed with Said Achmiz) puts footnotes as sidenotes in the margin on wide screens, shows link and footnote previews in popups on hover so you don't leave the page, and offers a reader-friendly dark mode and other options. Matthew Butterick's Practical Typography (2013) is a web book about typography that is itself an example of its own advice: a narrow serif column, careful spacing, and a pay-what-you-want model. Craig Mod's essays, from "Books in the Age of the iPad" (2010) and "Post-Artifact Books and Publishing" (2011) to "Future Reading" (Aeon, 2015), argued that digital books should stop imitating paper and start using what screens can do: connection, annotation and the edges around the text.

1. Margins are for notes (Gwern.net, Tufte CSS). On wide screens, unused margins become a place for notes, aligned to the line that references them. This uses the space that a limited measure creates, the same space Vector 2022 left empty.
2. Preview, don't navigate. Popups for links and footnotes let readers check a reference without losing their place. They need care: delay before showing, easy dismissal, and a tap equivalent on touch screens.
3. Typography as argument (Butterick). Practical Typography explains each rule (line length, point size, spacing, quotes) and demonstrates it on the same page. The site is its own proof.
4. Pay what you want for reading. Butterick asks readers to pay if the book is useful (or buy his fonts). The model keeps the page free of ads and pop-ups. Business model as reading design, again.
5. Post-artifact thinking (Mod). Mod argued that the most interesting changes in digital books happen around the text: sharing, annotation, collective marginalia, the network of readers, not in imitating page curls. Many products in this guide (Popular Highlights, Readwise, Medium highlights) are versions of that idea.

In the wild

• Gwern.netGwern Branwen
  Sidenotes, recursive popups for links and notes, extensive typography options. A personal site can out-design platforms because its writer cares about every detail.
• Practical TypographyMatthew Butterick, 2013–
  A free web book about typography, set to its own rules. The medium is the proof.
• Tufte CSSDave Liepmann
  An open stylesheet inspired by Edward Tufte's books, with sidenotes and margin figures. Patterns from print can be packaged for anyone to use.

Part four recap: connect the ideas

Feed readers taught the cost of counts. Medium taught reading time and the power of one good default layout. Wikipedia taught measure and wayfinding at scale. Audio products taught continuity across forms. The independent web taught what's possible when the margins work for the reader.

No reading product wins every criterion; the great ones choose which half (surface or system) to be best at, and refuse to be bad at defaults.

Below are illustrative scores using the chapter 1 scorecard. They are the opinions of this guide, formed from the decisions described in each chapter, not measurements. Your scores should differ; the value is in arguing with them. Under the table, if you saved scores in the chapter 1 lab, your own table appears too.

Standard Ebooks, Gwern.net and the reader modes are left out because they are a surface without a full system (or a system you supply yourself). Pocket and Omnivore are left out because they no longer run. Annotation is 0 for NetNewsWire and Wikipedia because they don't aim to offer it, which is a valid choice.

The pattern library

Every pattern in this guide, with the product that does it best and where it belongs in your own work. Treat it as a menu, not a checklist: a good product picks the few that serve its job.

In the wild

• Kindle vs Kobo2010s–2020s
  The same job, opposite strategies: closed system and convenience vs openness and control. Strategy decides which criteria you sacrifice.
• Reeder Classic and Reeder2023
  Two philosophies from one designer, shipped side by side. Sometimes the honest answer to "which is right?" is "for whom?".
• iA WriterInformation Architects
  A writing app with a reading-grade surface: tuned fonts, measure and focus mode. Reading patterns transfer to any text product. See Breakdowns: Software.

A good reading-product spec fits on one page: who reads what, when; the six moments and what the screen does in each; the defaults; and the few decisions you will defend.

This is where the breakdowns turn into design. You'll write a one-page spec for a reading product, or for the reading surface inside your own product. Keep it short on purpose. A spec that fits on one page forces you to decide; a twenty-page spec lets you avoid deciding. The template below follows the structure of this guide: job, scorecard targets, session moments, defaults, decisions with costs, and what you deliberately leave out.

The template

A worked example

Here is how the first blocks might look for a small product: a reader for long-form engineering blogs, built by one person. Note how the scorecard targets make later decisions easy.

In the wild

• Instapaper, 2008Marco Arment
  A one-person product whose whole spec could be: save in one tap, read beautifully offline, pay once. Small specs make small, excellent products.
• Reeder (2023)Silvio Rizzi
  One designer rethought the whole model around a timeline. A single strong decision can define a product.
• Standard Ebooks ManualVolunteers
  The spec is public and the product is consistent because of it. Written decisions scale.

Wrap-up

Practice assignment for the next two weeks

1. Days 1–3: score. Use five reading products you have access to (at least one e-reader app, one read-later or feed app, one web page). Save each in the chapter 1 lab with observations.
2. Days 4–5: session maps. Run the chapter 2 protocol on your two favourite and your own product. Shade the loud moments.
3. Days 6–7: quick fixes. On your own product: cap the measure, fix the default size and line height, add a typography pass. Measure before and after.
4. Days 8–10: one system pattern. Add one: reading time, live-preview settings, zero-cost capture, presence instead of counts, or export.
5. Days 11–13: capstone. Write the one-page spec and build the HTML Immerse prototype.
6. Day 14: reflect. Re-score your product. Write half a page: what changed in the numbers, and what changed in how reading it feels.

Reading list

• Books in the Age of the iPad (2010), Post-Artifact Books and Publishing (2011)
  Craig Mod · the clearest early thinking on which digital books should be "formless" and which need form, and on value around the text.
• Future Reading (Aeon, 2015)
  Craig Mod · why e-reading stalled and what was missing; a good critique to read beside the Kindle chapter.
• The "Future Book" Is Here, but It's Not What We Expected (Wired, 2018)
  Craig Mod · argues the real innovation happened in how books are made, funded and discussed, not in the reading screen.
• Practical Typography
  Matthew Butterick · free web book; the most usable rules for body text, demonstrated on its own pages.
• The Elements of Typographic Style
  Robert Bringhurst · the reference behind measure, leading and much of what good e-readers try to automate.
• Web Design is 95% Typography (2006)
  Oliver Reichenstein (iA) · short, opinionated, still right; read it with the Medium and Wikipedia chapters.
• Standard Ebooks Manual of Style
  Standard Ebooks · a real, public style system for prose; use it as a model for your own product's text rules.
• Reader, Come Home (2018)
  Maryanne Wolf · a neuroscientist on how screen reading changes deep reading; useful to remember what your product is protecting.
• The Coming Age of Calm Technology (1996)
  Mark Weiser and John Seely Brown · the origin of "calm" as a design goal; the frame behind counts vs presence.
• inessential.com
  Brent Simmons · decades of writing on building NetNewsWire: platform fit, restraint and open source.
• Readability.js (Mozilla, on GitHub)
  The code behind Firefox Reader View; reading it shows exactly how pages are scored for "article-ness".
• Desktop Improvements project pages (mediawiki.org)
  Wikimedia Foundation · the documentation and research behind Vector 2022; a rare public record of a large reading redesign.