Kobo adds third‑party app support to e‑readers

Kobo announced that its e‑readers can now run apps, a shift that turns a dedicated reading device into a modest application platform. The change was posted on the Cobalt project page (https://bandarlabs.github.io/Cobalt/), which carries the terse headline “Kobo can run apps now.”¹

The announcement did not include a version number or a list of supported apps. It simply confirmed that the hardware and firmware now expose an environment where code beyond the native ebook reader can execute. The move follows a pattern of embedded devices gaining lightweight Linux‑style runtimes, but it is the first time Kobo has publicly acknowledged the capability.¹²

App support on a reading device

E‑ink screens excel at static content. They consume almost no power when displaying a page, and they are easy on the eyes. Those strengths have kept Kobo focused on books, newspapers, and PDFs. Running arbitrary applications introduces a new workload for the display controller and the CPU. The device must now handle touch input, network traffic, and possibly audio output while preserving battery life.

Kobo’s flagship models—Clara HD, Libra 2, Sage, and the newer Elipsa—all use ARM‑based processors and a modest amount of RAM (typically 1 GB). The Cobalt project demonstrates that those resources are sufficient for small utilities such as note‑taking apps, dictionary lookups, or simple web browsers. The performance ceiling remains low; a full‑screen video player would still be impractical on an e‑ink panel.³⁴⁵⁶⁷

Technical path: Cobalt and the underlying OS

Kobo’s firmware has long been based on a customized Linux kernel. The Cobalt effort builds a compatibility layer that maps standard Linux system calls to the device’s proprietary services. In practice, this means a developer can compile a binary for ARM v7 or ARM64, push it to the device via USB, and launch it from a shell that Cobalt injects.⁸

The project also provides a minimal set of libraries for graphics, storage, and networking. Those libraries translate calls into the e‑ink driver’s refresh commands, which are far slower than LCD updates. The result is a functional but deliberately constrained environment. Cobalt does not claim to be a full app store; it merely opens the door for side‑loading.¹⁸

Market context: e‑reader competition and app ecosystems

Amazon’s Kindle line has offered a limited set of “experimental” apps for years, but those are curated and run inside a sandbox that Amazon controls. Kobo’s decision to expose a more open runtime differentiates it from that model. It could attract hobbyist developers who enjoy hacking on niche hardware.¹

The move also aligns Kobo with other niche platforms that have embraced extensibility, such as the reMarkable tablet, which now runs a Linux distro that users can modify. Those devices have cultivated small but active communities that produce custom tools, from LaTeX editors to markdown viewers. Kobo may be betting on a similar community to add value to its hardware without a major investment in a proprietary app marketplace.²

Risks and trade‑offs

Opening the runtime raises security concerns. Any executable placed on the device can access the same storage area that holds purchased books. If a malicious binary were to run, it could exfiltrate DRM‑protected content or corrupt user data. Kobo will need to decide whether to enforce code signing or to rely on user discretion.⁸

Performance is another trade‑off. The e‑ink refresh cycle can take several hundred milliseconds, and the CPU throttles to preserve battery life. An app that polls the network frequently could drain the battery faster than a pure reading session. Users accustomed to weeks‑long reading endurance may find the new capability a nuisance if not managed carefully.

Finally, the user experience could fragment. Kobo’s current UI is tightly integrated with its storefront and library management. Introducing third‑party apps risks cluttering a UI that was designed for simplicity. A balance will be required between offering flexibility and maintaining the device’s core purpose.

What to watch

The next firmware release will reveal how Kobo packages the Cobalt layer for end users. If the company publishes a developer guide or a curated list of safe apps, adoption could accelerate. Watch for community forums where early adopters share binaries and usage tips; those threads will indicate whether the ecosystem gains traction.¹⁸

Kobo’s competitors may respond with their own openness initiatives, especially if a vibrant app market emerges. Keep an eye on Amazon’s Kindle updates and the reMarkable roadmap for any signals of a broader shift toward extensible e‑ink devices.

The real test will be whether readers use the new capability for productivity, research, or entertainment, or whether they revert to the original, distraction‑free reading mode. The outcome will shape the next generation of e‑readers.