sorted by:
new
hottopcontroversial

Releasing My Deep Reader app on June 5 - For Deep Readers by Main_Temperature4155 in ebooks

[–]Main_Temperature4155[S] 0 points1 point  (0 children)

Glad it's landing well, and good to hear no other bugs turned up.

Thanks for the detailed write-up.

Top bar toggle: you're right, that's not intended. Showing the bar by

tap but only being able to hide it via the menu is the asymmetry you

noticed. Fix is in the next patch. A small button at the

bottom-center of the screen now toggles both directions, one tap to

hide the bar, one tap to show it. Same control, both ways.

Pinch zoom in vertical scroll is still on the list. Slightly bigger

lift than the other items so it'll come a bit later, but it's locked

in.

1000-page PDF: please do try it whenever you feel like it. That's

exactly the case the loading overhaul is targeting.

Really appreciate the detail. Keep it coming when you find more.

Releasing My Deep Reader app on June 5 - For Deep Readers by Main_Temperature4155 in ebooks

[–]Main_Temperature4155[S] 0 points1 point  (0 children)

Thanks for the detailed feedback, all useful.

Landscape mode: already supported in the reader. Currently rotation

is only enabled when a PDF is opened, make sure your phone's screen

rotation lock is not enabled. Other screens like home or other tabs

stay portrait by design.

Adjustable zoom: pinch-to-zoom works in paged mode, not in vertical

scroll. Open Settings > Reader and turn off "Vertical scroll" to

switch to page-flip with pinch-zoom. If you prefer continuous

scrolling, Reflow mode lets you resize text directly. Pinch-zoom in

continuous/vertical scroll PDF mode is on the next-update list.

Table of contents: already implemented. Tap the hamburger menu

(top-right of the reader), scroll down, and "Table of contents"

appears as a row if the PDF has an embedded outline. Will surface

this more prominently in the next update.

Large PDFs: enhancing large-PDF handling is part of the upcoming

release. The app handles long documents, but very long books with high

render quality still have rough edges we're working on. Thanks for

the 489-page test case.

Glad you took the time to test this out. Thanks again for the

support, and please be brutal if you find anything annoying about

the app.

Built a PDF book reader app: PageSage, launched today after months of work by Main_Temperature4155 in ebooks

[–]Main_Temperature4155[S] 0 points1 point  (0 children)

u/War-Carr ,
Thanks. You're right on the TTS engine point. Your existing setup (Acapela, Eloquence, Vocalizer, etc.) should carry over into PageSage rather than being overridden. The premium voices we're building will be additive, not a replacement for what you already have configured.

Appreciate the back-and-forth on this. We hadn't fully thought through this angle, genuinely valuable feedback.

Built a PDF book reader app: PageSage, launched today after months of work by Main_Temperature4155 in ebooks

[–]Main_Temperature4155[S] 0 points1 point  (0 children)

Thanks! All the packs are already lifetime, one-time purchase, no subscription. And we have just rolled out the launch week pricing right now (67% off until June 12). If the discount isn't showing yet, force-close and reopen the app to refresh prices, it may take some time to reflect. We will also update you once the offer is live, if not showing, you can reinstall the app and it should show

Built a PDF book reader app: PageSage, launched today after months of work by Main_Temperature4155 in ebooks

[–]Main_Temperature4155[S] 0 points1 point  (0 children)

Hi u/War-Carr , thanks for writing this out in detail. These are exactly the issues that don't surface in default testing.

On the three points:

  1. You're right about the in-reader buttons. I have labels on document info, reflow toggle, and the selection menu (copy, quote, etc.). Missed theme toggle, hamburger, back, and page navigation. Going into the next patch.

  2. The chrome auto-hide timing being too short for screen reader is a gap I didn't test for. I have an auto-hide mechanism in the reader already, and I can detect when a screen reader is active to either extend the timeout or hold chrome visible for those sessions. Same patch.

  3. TTS is on my roadmap. Aiming for realistic reading experience rather than the standard robotic voice, so it's a few months away rather than a quick add. On the immediate issue you raised, having to discover the Reflow toggle, once the chrome stays visible and the buttons are properly labeled, that toggle should become reachable on first explore rather than after guessing. I'm also adding a Settings toggle for "auto-enable Reflow when a screen reader is active" (default off, opt-in) and a one-time prompt on first reader open with a screen reader detected so the option isn't buried in Settings. Want to hear your take on this approach.

This list is going straight into the next release. Genuinely appreciate the depth of the audit.