Developing a read later client

whenders0n · 06-12-2025, 06:46 PM

Hi there,
Like many Kobo owners I was disappointed (though not surprised) at Mozilla's announcement. Unlike many, I'm an experienced mobile developer (though new to Kobo development). I'm wondering how feasible it would be to create an open source read later (to access Instapaper, Wallabag, etc) client.

Specifically, would cloning KOReader be a good place to start? Seems like it already has much of the tooling and functionality that I'd need. Would be an added bonus if I'm able to maintain cross-platform compatibility. Are there existing clones, or simpler projects out there that might be a better starting point and/or way to begin learning Kobo development?

If others are interested in this I'd welcome collaboration.

Thanks in advance.

(Sorry for the double post… accidentally posted this to the KOReader forum instead of this one!)

elinkser · 06-13-2025, 09:06 AM

The KOReader forum, AND the Kobo forum are not really bad places to post your idea.

KOReader runs on multiple platforms and therefore interests more than just Kobo users. Not only that, but its plugin system does not even require a clone, or even a compile! Their devs might have tips if you have a specific question about the debug process. Not only that, but there already IS a wallabag plugin!

The Kobo forum is relevant because Pocket users could give insight into their use patterns. There is in fact no shortage of Read-it-Later options - I've run a Shiori server and client on my Clara HD, modded a KOReader routine to execute an html-to-epub converter, and others just use Calibre or desktop plugins to save as epub to the cloud, for examples. The devil is in the details of what people find convenient.

Some options out there:

https://github.com/go-shiori/shiori#readme

https://codeberg.org/bins/sako-plugin

* Oh yes, there is also rmkit (C++), a super cool platform that supports some Kobo and Remarkable devices and has room for a spiffy read-it-later app.

** Actually, there is a great Gemini protocol (Simplified web protocol, not the AI engine) KOReader client, so you could contribute to the http/html to gemini proxies that already exist and help the battle against web bloatware!

whenders0n · Today, 02:53 AM

That's great, thanks! For now I have forked the koreader repo and am working off that. Screenshot of the work so far is attached.

It's currently implemented as a plugin, but I plan to either strip out or at least hide the main KOReader UI… my goal is something simple that ex-Pocket users will feel at home in and is as close to a "native" Kobo app as possible. We shall see if building on KOReader is the right approach… rmkit looks promising too!

elinkser · Today, 06:06 AM

If you want native Kobo integration, alot of work has already been put into infrastructure:

https://pgaskin.net/NickelMenu/

https://github.com/pgaskin/NickelHook

This kind of stuff allows you to embed menu items and functionality right into the Kobo ereader where Pocket users are accustomed to seeing it. No need to switch to the KOReader environment, although that would have certainly been a nice alternative because of Its open source portabiliy and maintainability.

If you're set on a standalone app, there are also the rust-based Plato, and user Szybet documented a Qt app example.

For me, the biggest issue was the complication of a server, plus being a relative simpleton, I never attempted all that.

06-12-2025, 06:46 PM	#1
whenders0n Junior Member Posts: 2 Karma: 10 Join Date: Jan 2025 Device: Libra Colour	Developing a read later client Hi there, Like many Kobo owners I was disappointed (though not surprised) at Mozilla's announcement. Unlike many, I'm an experienced mobile developer (though new to Kobo development). I'm wondering how feasible it would be to create an open source read later (to access Instapaper, Wallabag, etc) client. Specifically, would cloning KOReader be a good place to start? Seems like it already has much of the tooling and functionality that I'd need. Would be an added bonus if I'm able to maintain cross-platform compatibility. Are there existing clones, or simpler projects out there that might be a better starting point and/or way to begin learning Kobo development? If others are interested in this I'd welcome collaboration. Thanks in advance. (Sorry for the double post… accidentally posted this to the KOReader forum instead of this one!)

06-13-2025, 09:06 AM	#2
elinkser Addict Posts: 233 Karma: 146236 Join Date: Oct 2022 Device: Kobo Clara HD	The KOReader forum, AND the Kobo forum are not really bad places to post your idea. KOReader runs on multiple platforms and therefore interests more than just Kobo users. Not only that, but its plugin system does not even require a clone, or even a compile! Their devs might have tips if you have a specific question about the debug process. Not only that, but there already IS a wallabag plugin! The Kobo forum is relevant because Pocket users could give insight into their use patterns. There is in fact no shortage of Read-it-Later options - I've run a Shiori server and client on my Clara HD, modded a KOReader routine to execute an html-to-epub converter, and others just use Calibre or desktop plugins to save as epub to the cloud, for examples. The devil is in the details of what people find convenient. Some options out there: https://github.com/go-shiori/shiori#readme https://codeberg.org/bins/sako-plugin * Oh yes, there is also rmkit (C++), a super cool platform that supports some Kobo and Remarkable devices and has room for a spiffy read-it-later app. ** Actually, there is a great Gemini protocol (Simplified web protocol, not the AI engine) KOReader client, so you could contribute to the http/html to gemini proxies that already exist and help the battle against web bloatware! Last edited by elinkser; 06-13-2025 at 09:19 AM. Reason: rmkit/gemini protocol

Today, 02:53 AM	#3
whenders0n Junior Member Posts: 2 Karma: 10 Join Date: Jan 2025 Device: Libra Colour	That's great, thanks! For now I have forked the koreader repo and am working off that. Screenshot of the work so far is attached. It's currently implemented as a plugin, but I plan to either strip out or at least hide the main KOReader UI… my goal is something simple that ex-Pocket users will feel at home in and is as close to a "native" Kobo app as possible. We shall see if building on KOReader is the right approach… rmkit looks promising too! Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Touch How to read RSS and mails client in koboTouch?	Seninha	Kobo Developer's Corner	5	09-15-2015 02:09 PM
Need a PC client that syncs with my Moon + reader last read marks	zetsui	Android Devices	2	05-13-2014 02:15 AM
E-Mail client (read/send messages) app for PocketBook. or webmail?	pb611	PocketBook Developer's Corner	9	04-06-2013 01:12 PM

Today, 06:06 AM	#4
elinkser Addict Posts: 233 Karma: 146236 Join Date: Oct 2022 Device: Kobo Clara HD	If you want native Kobo integration, alot of work has already been put into infrastructure: https://pgaskin.net/NickelMenu/ https://github.com/pgaskin/NickelHook This kind of stuff allows you to embed menu items and functionality right into the Kobo ereader where Pocket users are accustomed to seeing it. No need to switch to the KOReader environment, although that would have certainly been a nice alternative because of Its open source portabiliy and maintainability. If you're set on a standalone app, there are also the rust-based Plato, and user Szybet documented a Qt app example. For me, the biggest issue was the complication of a server, plus being a relative simpleton, I never attempted all that.

Advert