[Feature request] (Android/iOS) Allow tapping screen to turn page in e-reader

[nerdpersonthing]

Currently, when using the e-reader mode to read (non-audio) e-books in the Android and iOS apps, the only way to turn the page forward or back is using a swipe gesture.

In most e-reader apps, as well as most e-reader devices (Kindle, Nook, etc), simply tapping different regions of the screen also works to turn the page in the same way. As an example, see the attached screenshot from Calibre's webserver.

It would be great if this could be implemented in Audiobookshelf for accessibility and ease of use.

One potential implementation that would make sense to me would be adding an option in the "Ereader Settings" menu - a selector labeled "Turn pages with:", with options "Tap", "Swipe", or "Both". In my opinion, "Both" should be made the default, as this is the behavior in the vast majority of other e-readers I have used.

[advplyr]

Have you seen settings in other ereaders that allow you to change how the page navigation works?

[nerdpersonthing]

Sure, here are a few examples.

Calibre doesn't actually have any options to configure its page navigation, to my knowledge - it just functions with both tap and swipe, and doesn't seem to have any way to customize that behavior.

Meanwhile, ReadEra (my preferred document reader on Android) does have some pretty extensive options to customize how its page navigation works - see the screenshots below.

(It refers to navigation by tapping as "Flipping by touch.")

Scheme 1:

Scheme 2:

Scheme 3:

I don't think customization this extensive needs to be in audiobookshelf; merely being able to enable/disable navigation that functions like Scheme 1, or Calibre's layout from the original post, would be sufficient IMO. (Though having the option to navigate via volume buttons as well would be nice.)

[KaiStarkk]

Agreed that detailed customization isn't needed, but a tap option would be very helpful as it prevents ghosting and works better on devices with lesser CPU / refresh rate.

[dathbe]

I support this. I would say that I think the later mock-ups in this thread are better than the one in the original post because most ereaders I’m familiar with will bring up the settings/options when you tap in the middle, but will turn the page if you tap the edge of the screen.

[goodeye1]

I would definitely be interested in this, the swipe is a big throw off for me coming from the kindle app and Libby where I’ve used the tap to swipe page setting for years.

[KaiStarkk]

Appears to be possible in upstream, although their docs are down. Helpful references:
futurepress/epub.js#46 (comment)
futurepress/epub.js#1400

[KaiStarkk]

Just noticed, the default behaviour in-app is now to turn the page instantly. Not sure if anyone feels this issue is still necessary? This has addressed my major concern of power draw and ghosting.

[nerdpersonthing]

Just tested it again, that doesn't appear to be the case for me on Android 0.9.76. Tapping the page still brings up the menu, with seemingly no option to instantly turn the page.

[KaiStarkk]

To clarify it used to be that there was a page turn animation which was the crux of the issue for me — you’re right that it doesn’t page on a tap, but it does now instantly page instead of animating which is an improvement from the power and e-ink standpoint

…

On Sat, 26 Oct 2024 at 4:04 PM, nerdpersonthing ***@***.***> wrote: Just tested it again, that doesn't appear to be the case for me on Android 0.9.76. Tapping the page still brings up the menu, with seemingly no option to instantly turn the page. — Reply to this email directly, view it on GitHub <#800 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANENUG3GWVWPFZRYHG2CXDZ5NEJZAVCNFSM6AAAAABJ2GG4RSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGQZDIMZRGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[dathbe]

Animation was not my issue. By far the most common interaction I have while reading (I suspect others too) is turning a page. That should be as simple as possible a gesture. Nothing is simpler than a single tap with a single finger. Instead, that brings up a menu I rarely need. And to turn the page I have to put the finger down, move it, then pick it up. So the request is regions on the screen so that menu only comes up if, say, you tap the top, bottom, or center of screen. Tapping left side will turn page back. Tapping right will turn the page forward. This is relatively standard reader behavior in my experience. But, to reiterate, it’s not secondary effects like battery life.

I’ve found the abs is not consistent about saving my reading position with books, so I’ve switched back to kavita for my e-reading (it does allow single tap page turning, too). I use abs exclusively for audiobooks now. But will give it another run when some of the kinks are worked out.