Project 34 / Physical

KOKU E-Paper Book

What if a digital book still had pages?

Concept artwork for KOKU E-Paper Book
Studio concept artworkE-paper / Product design
Project stageExploration
Available to exploreEngineering study
Creative directionAPX Build

The idea

Investigate the experience of turning actual electronic leaves instead of swiping a single screen. The first proof is a two-leaf reader with protected rigid or gently flexible display modules and a generous spine. A thin multi-leaf book is the long-term ambition, not an assumed manufacturable starting point.

What if a digital book still had pages?

The connection

The original question is physical: could the gesture of turning a page survive the move to electronic content? The answer depends as much on hinges, cables and weight as it does on software.

How it could work

01Book content
02Spine and leaf controllers
03Electronic pages

The dominant uncertainty is the moving electrical and mechanical interface. Flexible display technology does not mean an assembled screen, connector and cable can survive arbitrary folding. Obtain bend-radius, supported mounting and cable-life information from the actual module supplier. Do not make the panel itself the hinge. Use a mechanical hinge and a replaceable, strain-relieved interconnect with a controlled loop.

Start with one controller per module where that follows the supplier reference, a central content processor and sequential updates. A shared bus needs individually managed chip-select and busy signals plus verified logic levels. Long moving wires can change signal integrity. Compare that architecture against local leaf controllers only after measuring complexity and power.

What would prove it

Build one non-powered hinge coupon first and cycle it 1,000 times through the intended travel while checking continuity. Then build two powered leaves, update each independently and detect which page is open. Load a 20-page test document with numbered pages, alternating contrast and images. Turn pages in unexpected orders and disconnect power during an update.

Proposed gate: no cable continuity fault in the coupon test; 100 powered turns resolve the correct page without losing content; either leaf can be replaced without dismantling the other; the reader resumes with an explicit last-confirmed page after interruption. This test explores feasibility and is not a lifetime qualification.

The path to a complete build

  1. Obtain module mechanical specifications and make a full-size weighted mock-up.
  2. Prove hinge/cable motion before ordering multiple displays.
  3. Demonstrate two independent screens with deterministic page mapping.
  4. Evaluate readability, weight and turning comfort with three readers.
  5. Only then compare four-leaf, six-leaf and single-screen alternatives using measured cost and usability.
Open the engineering notebook

Components, interfaces and calculations

Build a dimensioned book mock-up, two documented display modules, a development processor, hinge parts, page-position sensors, replaceable cables and a USB power arrangement. Defer the battery and custom PCB. Size the spine from actual connectors, cable loops and bend clearance; do not compress the layout to match a render.

Measure mass per leaf and opening torque. Track total energy per page update and idle power. A book with n screens multiplies display cost, replacement exposure and cable count; use cost = n × (module + driver + leaf structure) + spine electronics + assembly + rework. Obtain quotes before making a multi-leaf cost claim.

Scope and development questions

Allow 8–12 sessions for a two-leaf feasibility rig, excluding supplier lead times. Required decisions are leaf size, number of independently visible pages, monochrome versus colour, document formats and acceptable book thickness. Stop or redesign if suppliers cannot provide a viable moving interconnect or the weighted mock-up is unpleasant to hold.

Reference basis

This case study develops the project concept into a proposed build route. Numeric gates are design targets; completed hardware tests are not claimed.

From the notebook to the world

See a connection?
Let’s make it happen.