Visually indicate why Koreader cannot be enabled

[imnotjames]

What would you like Grimmory to do?

Make it visually apparent when trying to turn on koreader sync that it's not available because the credentials are not set.

While the docs instructions do denote that you have to set the username and password first ( https://grimmory.org/docs/integration/koreader ) it's not clear to users why they can't enable koreader.

Either visually represent the username / password in a red outline or show a tooltip or shake them or otherwise make it clearer that something is wrong.

What problem does this solve for you?

Users are confused why they cannot enable Koreader Sync

Anything else?

No response

Want to help out?

I'm happy to help test and give feedback

Before submitting

• I've searched existing discussions and this hasn't been suggested yet
• I've reviewed this report and have completed it as fully as I can

[zachyale]

Not to block this, but maybe there's a better flow we could design that makes this more intuitive to the user instead of just shifting the onus onto an animation? Just spitballing, but perhaps when enabling an integration for the first time (like OPDS, Komga, KOReader, Kobo, etc.), we break things down into just a high level 'enabled' toggle, and have a CTA to "Setup" the integration for the first time, taking them through a flow? Would also reduce our dependence on users reading documentation before setting up a feature by making it more intuitive. Definitely more work than just an animation, but food for thought.

[imnotjames]

I don't think it's blocking - the point of feature discussions like this are to bring discussion into it & hone the ideas. :)

Yeah, I agree - there could be much better flows for these kinds of things.

[Abu5217]

Because I didn't read the manual I had issues. Because I am stubborn they lasted longer than they should have. Basically, I quickly skimmed the instructions for setting up KOReader Sync last night, then tried to set it up today. I clicked the Enable KOReader Sync toggle several times, wondering why it would not change. Then I saw the Edit button way down at the bottom of the section. I clicked it, then went back to the toggle.

Finally I figured out that maybe I need the credentials first, and that, of course, worked. Without reading the manual it was not clear why I couldn't enable the sync as I am more of a top-down person, so I assumed that I would work down the form from top to bottom and submit.

The above idea, a top level toggle followed by a directed flow would be very, very nice.

Thanks for taking the input.

[imnotjames]

From #1618 by @celery-4

On the KOReader Sync Settings (Settings>Devices>KOReader Sync Configuration>Sync Configuration), I think it makes more sense to move the two toggle switched to be at the bottom of the optional fields.

I saw 1 other person a little thrown by the need to go down to edit first, enter in the Username, Password, API Path, then being able to toggle the switches. To me, this data process is structured in reverse. You start at the bottom (Edit) and fill things out on your way up, so you can click the sliders at the top. Maybe it is worth putting "Edit" at the top too?

I would be happy to update the documentation once complete.