CrossPoint Reader adds plug-in support, bringing library ebooks to Xteink pocket e-readers

CrossPoint Reader, a free alternative firmware for Xteink's X3, X4, and X4 Pro pocket e-readers, now supports third-party plug-ins — and the first community-built plug-in gives those devices access to DRM-protected ebooks borrowed through OverDrive's Libby library app or purchased from retailers like Kobo. The feature is in beta and open to anyone who wants to try it, according to The Verge.

This fills a gap that has limited the appeal of Xteink's hardware since launch. The devices previously required users to find DRM-free ebooks on their own, with no straightforward path to the library lending ecosystem that most readers in the US and parts of Europe rely on. Xteink's own product pages confirm the X3 does not list Libby among supported services, and the X4 Pro is explicitly described as neither an Android tablet nor a Google Play device — ruling out the workaround some e-reader owners use to install the Play Store on Android-based devices.

The plug-in, called "Protected Content," runs through CrossPoint Reader's built-in web server and lets Xteink devices open ebooks protected by Adobe Digital Editions DRM. DRM, or Digital Rights Management, is the copy-protection layer that publishers require on most library and retail ebooks. Using the plug-in requires a free ByteBooks account or a converted older Adobe Digital Editions account to authorize the e-reader for protected content. The workflow mirrors what desktop-based Adobe Digital Editions users have done for years: borrowing a book through Libby produces a small ACSM file, which an authorized reading app then uses to fetch the actual DRM-protected EPUB. CrossPoint Reader now handles that authorization and download flow on the device itself.

There is a hardware constraint. Xteink e-readers use low-power ESP-32 processors — the same family of microcontrollers popular in DIY electronics projects — and cannot search or download ebooks from Libby directly. Users will still need a phone or computer running the Libby app to browse, borrow, and obtain the ACSM file, then transfer it to the e-reader. The reading happens on the Xteink device; the discovery and checkout steps stay on a companion device.

Both the X3 and X4 ship with Xteink's proprietary firmware, which is minimal — providing access only to books and settings, with no app ecosystem or browser. CrossPoint Reader replaces that firmware entirely, and its new plug-in architecture suggests the Libby integration is a first step rather than a one-off feature.

The hardware itself is built around portability. The X3 is a 58-gram, 3.7-inch device with physical controls and local-file reading. The X4 Pro weighs 72 grams, measures 5.95mm thick, and adds a built-in front light with adjustable brightness and warm/cool color temperature settings, plus a touchscreen for navigation. These are devices designed to be carried in a pocket, not propped on a desk.

The ESP-32 platform that makes the form factor possible is also what constrains the software. These are microcontrollers, not the application processors found in phones and tablets; there is no headroom for a full operating system, a browser engine, or a native Libby client. CrossPoint Reader's approach — a lightweight firmware with a web server that handles DRM authorization and file management through plug-ins — fits the hardware's capabilities while working around its limitations.

The broader context here is about access, not performance. Pocket e-readers have existed for years, but most have either been tied to a single ecosystem (Amazon's Kindle being the obvious example) or restricted to sideloaded, DRM-free files. What CrossPoint Reader's plug-in architecture does is give devices outside the major ecosystems a practical path to the same library-lending and retail-purchase workflows that mainstream e-readers support. For readers who want a pocket-sized device but are unwilling to abandon Libby or DRM-protected purchases, that is a meaningful gap closing.

The beta status matters. DRM handling is fragile by nature — Adobe's ACSM/EPUB workflow depends on authentication servers, token refresh logic, and licensing rules that vary by publisher and library system. Anyone testing the plug-in now should expect rough edges, particularly around loan expiration and authorization recovery if a device is reset or an account is re-provisioned. CrossPoint Reader's project site lists the Protected Content plug-in under its tools section.

In my view, the more interesting signal is the plug-in architecture itself. If CrossPoint Reader sustains community development, it could become a general-purpose middleware layer for low-power e-ink hardware — a niche that the major players have largely ignored. The ESP-32 e-reader category has been a hobbyist corner of the market, limited by software as much as by hardware. A firmware with a plug-in system and a web server changes what these devices can do without changing what they are.