Reading on E-Ink Devices: Boox, Kindle Scribe, reMarkable

Your Boox is to read documentation.

My marriage is now stronger and my eyesight isn't worse. I'm not making this up.

The dev community has been quietly adopting e-ink devices for technical reading over the last few years. The math finally makes sense: the devices are good, the docs are PDF-able, and screen fatigue is real.

If you've been considering it, here's the honest take.

Table of Contents

• The E-Ink Case for Devs
• Comparing Three for Technical PDFs
  • Boox (Note Air, Tab Ultra, Palma)
  • Kindle Scribe
  • reMarkable (2 / Pro)
• Code-Block Readability
• Annotation Workflows
• The "No Laptop Weekend" Reading Routine

The E-Ink Case for Devs

Three reasons that hold up:

1. Eye strain. Screens are emissive. E-ink is reflective (ambient light bounces off, like paper). After a full day on a laptop, an e-ink device feels like a vacation. Same words, none of the eye fatigue. There's a whole separate guide on eye strain.

2. Focus. E-ink devices, even the ones running Android, are slow at most things. That sounds like a bug. It's actually a feature. The friction of "switching to Slack" on an e-ink device is enough that you don't.

3. No notifications. Most e-ink devices either don't run notifications (Kindle, reMarkable) or you can disable them at the OS level (Boox). Reading, undisturbed, like it's 2008.

The combination is what makes e-ink genuinely different from "iPad with a matte screen protector."

Comparing Three for Technical PDFs

I've tried all three. Here's the take.

Boox (Note Air, Tab Ultra, Palma)

Strengths: Open Android. Sideload any PDF reader. Side-by-side reading. Color models exist (Boox Tab Ultra C). Good at code blocks because of color.

Weaknesses: Battery life shorter than dedicated readers. Some Android jank. Not as polished as Kindle hardware.

Best for: Devs who want flexibility and don't mind tinkering. Multiple PDF readers, custom keyboard shortcuts, Calibre integration. Most "power user" features live here.

Kindle Scribe

Strengths: Best-in-class typography. Excellent battery (weeks). Solid for long-form reading. Pencil for annotation. Tight Amazon ecosystem.

Weaknesses: PDF rendering is okay, not great (small fonts can be hard to read). Limited side-by-side. The Amazon walled garden if you care about that.

Best for: Devs who already live in the Amazon ecosystem and want a "read this PDF" device, no tinkering.

reMarkable (2 / Pro)

Strengths: Beautiful writing experience (the "paper feel" is real). Distraction-free OS. PDF annotation is the best in this category.

Weaknesses: PDF reading (not annotating) is slower than Boox. No third-party apps. Subscription tier for some sync features.

Best for: Devs who want to write on technical PDFs. ADRs, design docs, drafts of new features. The reMarkable shines as a notebook with PDF backdrops.

Code-Block Readability

Honest tests on each device for code-heavy PDFs:

For code-heavy reference PDFs, color matters more than I expected. A grayscale syntax highlight is fine but a color one (especially Boox Tab Ultra C) is much closer to the on-screen experience.

If you're mostly reading prose-style docs (Vue handbook, Rust book, Postgres manual), grayscale is fine. Save the money.

If you're reading API references with dense code samples, color is worth the upgrade.

Annotation Workflows

What I do, by device:

Boox: Highlight in the PDF reader. Margin notes via stylus. Sync to Google Drive. Read in Calibre on desktop later.

Kindle Scribe: Native highlights and Pencil notes. Sync to Amazon's notebook view.

reMarkable: Direct on-PDF annotation. The system is designed for this. Export annotated PDFs back to your laptop.

For PDF reading: all three work.

For PDF annotating: reMarkable wins. The whole device is built for it.

For my workflow (read first, annotate sometimes), Boox Tab Ultra C is the daily driver. Different person, different optimum.

This connects to the print workflow — annotation is annotation, the medium varies.

The "No Laptop Weekend" Reading Routine

Where e-ink really earned its place: weekends.

Friday evening, I sync 4-5 PDFs to my Boox. Generated via OfflineDocs earlier in the week.

Saturday and Sunday, I read on the couch. No laptop. No phone. Just the device and a coffee.

Two hours of focused, undistracted technical reading on a Saturday morning is more learning than four hours at a desk during the week, every time. The medium changes the behavior.

The PDFs come from anywhere — a Vue handbook, a Rust book, a TypeScript reference. The platform doesn't matter. The discipline of "Saturday is for the e-ink device" does.