To be clear, it’s definitely improved some in that time, but there still yet remains plenty of room for further improvement.
Google seems extremely reticent to have anything resembling strong opinions in Android’s API design and so there are still many corners in which well-supported, fully fleshed out “correct” options are absent.
I was a bit dumbfounded by the original KoReader browsing UI, I would have expected something more organized, but I thought "maybe it's just a setting I haven't discovered yet".
It looks like I need one of those instead. Will do when I have some time.
Does this support collating books of the same series together?
It does not have any sort of "whispersync" but, ironically?, I feel like whispersync could be recreated with things like Whisper and parsing the epub/whatever to line up progress. BookOrbit is in active development from what I can see (I'm not connected to the project, just a happy user) and it wouldn't surprise me if that was a feature in the future. It's something I've mulled over building for a while (even before Whisper).
For my Audiobooks I don't use BookOrbit because my setup is:
- Buy on Audible
- Rip DRM off
- Add to Plex
- Use Prologue (iOS only) to listen
And I freaking love that setup so I'm not looking to replace it currently.
> Unfortunately on MacOS it seems you have to use Amazon's app to access the filesystem.
Hmmm not really my experience, unless it's a new thing. I am still able to access it via finder. Although I need to exit KoReader first and go back to the stock UI.
As someone who thought the same (stock was enough for me) until I had some free time and switched, here are some things I'm really enjoying, in no particular order:
- Format support: EPUB, CBR/CBZ (comics, graphic novels), PDF
- Dark mode
- Fully programmable gestures and shortcuts
- Automatically syncs with my readeck instance (think readitlater/instapaper) to dowload the articles I save for example here on HN
- Calibre integration over wifi
- RSS/Atom
- Custom dictionaries
If you are into manga, there is an extension for directly downloading them on the device
Because most of the page is dark, with light only coming from the text, the total light emitted is much less. That makes it less annoying to my wife, when I'm reading before going to sleep.
this is the worst kind of pedantic engineer comment that seems to infest this site. they're obviously talking about the frontlight. dark mode reflects much much less light back at the user through the lightguide because the dark bg absorbs more of the light.
It wasn't obvious. My thought process was that they were equating ereaders with eink displays, and they had a non-eink ereader. To me, emitting light and reflecting light are completely different.
(I suppose I'm not supposed to feel complimented by the term 'engineer'? I'm not trained/experienced in any engineering discipline, not even software engineering.)
If you want pedantic ridiculousness, well, notice that I never said that the e-ink emits light. It does, however reflect light back from the device's frontlight. The device taken as a system most certainly emits light, but less so when in dark mode.
I have no idea but users seem to like it despite all the ghosting.
The reason I use koreader is because it can sync my progress on disparate devices. I have a normal sized kobo and also a phone sized viwoods eink device.
Unfortunately, this video isn't as apolitical as you are saying. I happened to watch this response recently, IMO it's very well argued: https://youtu.be/UjmsfOXy5oM
Any idea why the extension failed? I go to great lengths to make my blog a good web citizen (semantical, working without JS etc.), and that it isn't parseable would be a thing I need to fix.
I was an Android developer 15+ years ago, and this is exactly what made me move away into backend.
Interesting that it's still like that after so much time!
reply