KOReader

I'm immensely thankful for koreader - it improves the reading experience so fundamentally that it literally drives my purchasing decisions. I got a remarkable 2 precisely because it was known to run it well. When I got a new kindle, I went for a refurbished one hoping it'd be one FW version behind (it was! lucky me) so I could jailbreak it immediately, and run koreader.

Which reminds me:

- I'm still a primitive user. Sync reading state, reflow, calibre link, yes, but I'm at maybe 10% of the features, might even be an overestimate. I may finally have to cave in and go through its manual

- I literally endure calibre because that's how I feed koreader. Any alternatives?

- Is there really no practical way to mark a book as read other than give it a star rating or a custom tag?

- Does anyone know of anything coming close to this experience on an iPad?

- I've never given them a cent or contributed a line of code or even filed a bug report. That changes now.

Because I don't own any that I want to use.

I always have a phone, a laptop, a tablet or a desktop to hand. The tablet is a great device for reading comics as well as books. The phone is a terrible device for reasing comics, but fine for books.

[dead]

> The stock software in Kobo and kindle can be used within minutes because they don't have a lot of features/options.

Afaik koreader itself does not support stylus while the default reader in kobo does (somebody made a plugin lately but not sure how stable it is). Not to say that koreader is not amazing, but it does not mean that FOSS always has strictly more features. If koreader had strictly more features and I wanted some of them I would choose that. But I also right now want to use the ereader to read books and take notes, not tweak plugins and configurations. I have been in this "power user" loop where I spend more time with configuring rather than doing the thing, and I am a bit more selective with when this makes sense to me.

> I think the issue of bad UX and OSS are comorbid because

I think UX is simply harder when you're not leading the user by the nose to your most profitable features, and removing or obscuring the others. Commercial UX is more akin to advertising than UX, so there's no wonder that it makes very clear the few affordances that it offers (and bizarre when it doesn't, like the "flat" period.)

The other problem with FOSS UX is that millions of dollars haven't been put into it (literally: 5 developers = 1 million dollars/year.) The wonderful benefit of FOSS UX is that you have plenty of time to learn it, because every feature is already there, no one is forcing you to upgrade, and no one is moving things around and deleting things because it is more profitable to them.

Commercial UX had better be good enough to learn basic functionality quickly, because it's going to be completely recycled every year. It also doesn't want you to learn anything too deeply, because then you might become a (gasp) "power user" and make unprofitable demands.

Imagine using the same type of software (e.g. an mp3 player) for a couple dozen years and thinking that it's a hassle to figure out how to learn it. Imagine being boiled like a frog to relearn how your mp3 player works every couple years for a couple dozen years, and dreaming you've saved some sort of time or effort. Imagine you've used mp3 players for a couple dozen years, you still don't know what an mp3 is, you don't know what a file is, and you don't know how to get your mp3s back after switching your mp3 player without rebuying them. Eventually you switch to streaming, give up making any decisions, and take whatever the marketers prefer.

This is "good" UX.