The E-Reader Is Not Dead — It’s Just Been Waiting for the Right Sidekick
Here’s the thing that keeps me up at night as someone who runs multiple social accounts and manages content pipelines: the most valuable asset I have isn’t my posting schedule or my follower count. It’s my attention. And attention is precisely what the modern creator economy is designed to steal from you, one algorithmic notification at a time. Every time I sit down to review a long-form article, read through a research paper for a video script, or check the logs of an AI agent that’s been generating content drafts overnight, I’m doing it on a glowing laptop screen that’s also pinging me with Slack messages, Instagram DMs, and the latest X drama. It’s a recipe for fragmented thinking.
So when I see a tool that promises to move that deep-work reading and approval workflow onto an e-ink device — a device with a month-long battery life and zero social media notifications — my interest is immediate. This isn’t just a niche hardware hack. It’s a commentary on how we operate as digital professionals. The product is Cobalt, a platform and SDK that turns Kobo e-readers into something closer to a minimal Android device. For social media managers and indie founders drowning in content consumption, this isn’t about reading books. It’s about reclaiming cognitive space while still getting the job done. This essay is about why that matters, where it fits in your workflow, and where I think the hype outpaces the reality.
The Real Problem: Your Phone Is a Terrible Reading Device
Let’s be brutally honest about the operational reality of being a content creator in 2025. Your phone is a slot machine disguised as a communication device. When I’m researching a video essay on TikTok trends, I need to read long-form reports from Pew Research, sift through platform documentation, and review comments from a Reddit thread that’s 2,000 posts deep. Doing that on a phone means fighting a losing battle against the notification shade. Doing it on a laptop means sitting in the same chair I’ve been in for eight hours, which is a recipe for burnout.
The maker of Cobalt, manish kumar, frames the problem in a way that resonates with me: we read a lot more than books daily — forums, long-form articles, research papers, coding agent logs. The traditional workflow for getting this content onto an e-ink display is absurd. You search for the content, download it, convert it on a laptop, and then sideload it onto the device via USB or a clunky cloud sync. It’s a process that takes so long you might as well just read on the laptop.
Cobalt’s approach is to build an app store and SDK directly for Kobo devices, which are historically locked-down Linux tablets that only read books. The team claims to support a range of devices including the Libra Color, Libra 2, Clara BW, Elipsa 2E, Clara HD, and Clara Color. This is significant because Kobo has been the “other” e-reader for years — the one that people buy when they don’t want to be locked into Amazon’s ecosystem but still want a decent reading experience. Now, it’s being repurposed as a low-cost, low-distraction terminal for the rest of your digital life.
Why This Matters More for TikTok Creators Than LinkedIn Ones
Let me draw a distinction that I think is critical. If you are a LinkedIn thought leader — and I mean that in the most respectful way possible — your content is text-heavy, and your workflow is probably already optimized for desktop. You write posts in a text editor, you schedule them with a tool like Buffer or Hootsuite, and you rarely need to read dense research to produce a 500-word post about leadership.
But if you are a TikTok or YouTube creator, your research phase is massive. You are pulling from multiple sources to build a narrative. You are fact-checking claims. You are reading comment sections to understand the discourse around a topic. For me, the most painful part of the content creation process isn’t the editing — it’s the reading. I need to consume 10x more content than I produce to have a chance at making something original.
Cobalt’s pitch — specifically the arXiv browser and reader for research and the RSS discovery & reader — directly addresses that bottleneck. If I can have a device that sits on my desk, syncs my RSS feeds, and lets me read through a stack of articles without the glow of a backlit screen, I can do my research phase in a more focused, deliberate way. The fact that it also has an audiobook generator using deep research and ElevenLabs API is a nice touch for turning articles into something you can listen to while walking the dog, though I’ll get to the caveats on that later.
How Cobalt Differs from the Incumbents
When I look at the landscape of tools vying for the “distraction-free reading” niche, I see a few clear categories, and Cobalt doesn’t fit neatly into any of them.
First, there are the note-taking apps like Notion or Obsidian. These are powerful, but they are still fundamentally desktop/mobile apps. They are not hardware. They don’t solve the screen problem. They just organize the chaos.
Second, there are the “read-it-later” services like Pocket or Instapaper. These are great for clipping articles, but they still assume you’ll read them on a phone or a tablet. The reading experience on an iPad is marginally better than a phone, but it’s still a glowing rectangle that offers a million other distractions.
Third, there are the e-reader native solutions. Amazon’s Kindle has a “Send to Kindle” feature that lets you push web articles to your device, but it’s clunky and doesn’t have an app ecosystem. The Kindle is a closed system. You are at the mercy of Amazon’s software team.
Cobalt is trying to be the Android of e-ink. It’s an SDK that lets developers build apps for Kobo, and it comes with a curated app store. This is a fundamentally different approach. Instead of asking the manufacturer to build 50 different features, it opens the platform to the community. This is the same playbook that made Android successful against iOS in the early days — not necessarily better, but more open and flexible.
The inclusion of a Claude Code / Codex controller and a terminal is a huge differentiator. This is not a tool for reading novels; it’s a tool for managing AI workflows. For a creator who uses AI to draft scripts or generate social posts, being able to approve a Claude Code output from an e-ink device is a game-changer. You are not sitting at your desk waiting for the terminal to finish; you are on your couch, reading the output on a screen that doesn’t fry your retinas, and you tap “approve” when it’s done.
The “Sidekick” Workflow: Approvals Without the Laptop
The maker’s comment about having a “sidekick for approvals streamed to the Kobo” is the most compelling use case for me. In my own tests of similar tools, the bottleneck is always the approval loop. I use AI to generate a batch of 30 social media posts. I scan them on my laptop. I edit them. I schedule them. The problem is that I have to be present at the laptop to do that scan. If I’m out of the office, or if I’m just trying to take a break from the screen, the workflow stalls.
Cobalt’s potential to fix that is significant. Imagine a workflow where you have a Claude Code agent that generates the posts, and then sends them to your Kobo. You read through them on the e-ink display, mark the ones you like, and the agent takes your feedback and schedules them via a tool like Metricool or Later. That’s a fully asynchronous workflow that doesn’t require you to be chained to a desk. The team claims this is possible, and based on the SDK description, it seems technically feasible. But the execution will depend on how well the Kobo’s hardware handles the network requests and how responsive the app is. E-ink is not known for speed.
What Creators and Social Media Teams Can Borrow From This
Even if you never buy a Kobo, the philosophy behind Cobalt is worth stealing. Here are three operational lessons I’m taking from this launch.
1. Separate Consumption from Production. The biggest productivity leak in my workflow is context switching. I read an article, then I write a tweet, then I check the analytics, then I read another article. Cobalt forces you to separate the reading phase from the doing phase. You can apply this principle without any new hardware. Use a dedicated browser profile for research. Use a tool like Pocket to queue up articles, and then schedule a block of time to read them with your phone in another room. The device is a catalyst, but the habit is the real change.
2. Optimize for the Approval Loop. The most expensive time in a content operation is the time when a senior person has to review and approve work. Whether it’s a script, a video edit, or a batch of posts, that approval is a bottleneck. Cobalt’s pitch is to make that approval loop more accessible and less punishing. You can borrow this by simplifying your own approval process. Instead of asking for comments in a Google Doc, ask for a thumbs up or down on a specific Slack message. Reduce the friction of the “yes/no” decision, and you’ll move faster.
3. Low-Power Background Processes. The idea of a “month long battery life” is a feature I didn’t know I needed until I saw it. Your phone dies in a day. Your laptop lasts a few hours. A device that lasts a month is a device that is always on, always available, and never needs to be charged in a panic. For a social media operator, this is the ultimate “always-on” dashboard for your reading queue. It’s a reminder that not every task needs a high-powered computer. Some tasks are better served by a low-power, dedicated device.
Where the Math Breaks: My Honest Judgment on Cobalt’s Shortfalls
I want to be clear: I am excited about this, but I am not a blind optimist. There are significant limitations here that you need to consider before you rush to buy a Kobo.
The Hardware Ceiling. Kobo devices are not fast. The processors are designed for page turns, not for complex applications. The terminal and Claude Code controller might work, but they will be slow. If you are used to the snappy response of a modern laptop terminal, the e-ink experience will feel like watching paint dry. This is fine for reading and approving, but it’s not a replacement for a development environment. In my experience, anything that requires constant scrolling or rapid input is a pain on e-ink.
The App Ecosystem is Nascent. The team lists a handful of apps, but this is not the App Store. There is no Twitter client, no Instagram scheduler, no robust web browser. The apps that exist are curated for a specific use case. If you need something that isn’t in the store, you have to build it yourself using the SDK. That’s a high barrier for most creators. The “app store” is a promise, not a reality yet. The success of this platform hinges entirely on developer adoption, and that is a notoriously difficult thing to bootstrap.
The Audiobook Generator is a Liability. The team claims it can generate audiobooks using deep research and ElevenLabs API. This sounds cool, but it raises a massive copyright and quality red flag. Generating an audiobook from a copyrighted article or book without permission is legally dubious. Furthermore, AI-generated narration, while good, still lacks the emotional nuance of a human narrator. I would be very careful about using this feature for anything other than your own private notes. The team claims it works, but I’d bet the quality is inconsistent.
The “Who is this for?” Question. This is not a tool for the average social media manager. This is a tool for a specific type of operator: someone who is technically savvy, works with AI agents, and has a high volume of text-based research. If you are a food blogger who just wants to schedule Instagram posts, this is overkill. You are better off with a standard scheduler and a good pair of blue-light blocking glasses. Cobalt is for the power user, the indie hacker, the person who lives in the terminal.
The “10x” Problem. The launch page mentions the team was recently #1 on Hacker News with 650+ votes. That’s a great signal for the maker, but it doesn’t mean the product is ready for primetime. It means the concept is interesting to a technical audience. I would treat any claims of “revolutionizing” your workflow with skepticism until you’ve spent a week using it. The concept is solid, but the execution is still early.
Why LinkedIn Creators Should Probably Skip This (For Now)
I mentioned earlier that TikTok creators should care more, but let me flip the coin. If you are a LinkedIn creator, your content is usually short-form text, and your research is probably done via a quick Google search or a news aggregator. You don’t need an arXiv browser. You don’t need a terminal. You need a clean writing interface and a reliable scheduler. The Kobo is a reading device, not a writing device. While you could use the terminal to run a script, the lack of a physical keyboard makes writing on it a chore. You are better off sticking with a laptop for writing and using your phone for quick engagement. The Cobalt platform, in its current state, is not designed for the LinkedIn text-post workflow. It’s designed for deep consumption and approval, not creation.
What I’d Watch / Test Next
I’m not ready to throw my laptop in the trash, but I am ready to run a specific experiment. Here is what I would test this week if I had a Kobo and the Cobalt SDK installed.
1. The RSS-to-Script Pipeline. I would set up a workflow where my RSS feeds for marketing news are filtered through an AI agent that summarizes the key points. That summary gets sent to the Kobo. I read the summary, and then I dictate my initial script ideas into a voice memo on my phone. The goal is to see if I can do the “idea generation” phase entirely away from a screen.
2. The AI Approval Loop. I would generate a batch of 10 tweets using Claude Code, have them pushed to the Kobo, and then approve or reject them from the e-ink screen. The test is not whether it works — it will work — but whether the friction of the e-ink interface makes me more or less likely to actually do the review. If the screen is too slow, I’ll just go back to my laptop.
3. The Battery Life Reality Check. The claim of a “month long battery life” is a huge selling point. I would test this by leaving the device on with the Wi-Fi on and the RSS reader refreshing every hour. I’d bet the battery life drops significantly compared to airplane mode, but if it still lasts a week, that’s a win.
4. The Sideloading Pain. I would test how easy it is to get my own content onto the device. The team mentions sideloading is a pain point they are solving, but I want to see if the SDK makes it easier than the old USB-cable method. If it’s still a hassle, the platform loses a lot of its value for me.
5. The Build-Your-Own-App Threshold. The SDK is the most interesting part to me. But I’m not a developer. I would look at the SDK documentation and see how much code is required to make a simple “read this URL” app. If the barrier to entry is too high, the app store will remain a ghost town, and the device will become a paperweight.
My final verdict: This is a “watch closely” product, not a “buy immediately” product. The concept is a breath of fresh air in a hardware space that has been stagnant for years. It challenges the assumption that we need a glowing screen for everything. But the success of Cobalt depends on the community. If developers build the apps we need, this could be the best $100 investment in your focus and attention since you bought a pair of noise-canceling headphones. If they don’t, it’s just another e-reader. I’m rooting for the former, but I’m prepared for the latter.
