(New) App Feedback
-
After upgrading my Pixel 6 to Android 13 I now see glyphs before each paragrah:
These were not visible before I upgraded.
I will also stress that the App does not recover from a connection loss.
Even after the connection is restored all requests in the App continue to fail.
This makes the App VERY annoying to use out and about. -
Generally, I like the app.
There is however one feature I'm really missing.
Unlike other reader apps, you can't use the volume buttons to scroll up/down (parts releases) or switch pages (manga). I tried to use third party apps to add that feature, but they had to run the entire time, taxing the battery. -
The website provides the following information. It’d be convenient if the app provided it as well.
-
The date that a book will expire.
-
The number of parts a book will have.
-
When the last part of a book is released, it’d be helpful if the app’s “Releases” display added “FINAL” to the part number, like what is done on the website’s “Calendar” page.
-
-
@rock3tz said in (New) App Feedback:
After upgrading my Pixel 6 to Android 13 I now see glyphs before each paragrah:
It might be a long shot, but have you tried restarting your phone?
When I upgraded to Android 13 I had to do an additional restart of my phone to get all apps to show up in my app search and I wonder if it's a similar cache issue for you.
-
@Shiny
Tried that, still happens:
-
@rock3tz said in (New) App Feedback:
@Shiny
Tried that, still happens:Okay just did some investigation on my Pixel 6 which uses Android 13. Some fonts work and some result in the issue you describe.
Working: Literata, Arbutus Slab
Broken: Vollkorn, Roboto, Lato, Noto Sans, Antoka
A workaround for now is to change to a working font in JNC app settings.
-
@Shiny @rock3tz I cannot see the screenshot, but I'm guessing the glyphs, or tofu as they're also called, are either diamonds with question marks in them or rectangles. People who've encountered them before probably know what they mean - the font that is being used to render the text does not support the unicode character in the text.
In the novel reader, in order to indent text, three unicode tab characters are inserted at the beginning of each paragraph (
\x{9}\x{9}\x{9}). I didn't encounter the tofu issue while developing/testing on either iOS or Android. Normally, if the selected font doesn't support the character, the fallback OS font should. I'm honestly surprised that such a basic unicode character isn't part of the fonts, and not sure what changed with Android 13 yet, but I'll make sure to test on an Android 13 simulator before releasing the next update to the app. -
@chocolatkey said in (New) App Feedback:
@Shiny @rock3tz I cannot see the screenshot, but I'm guessing the glyphs, or tofu as they're also called, are either diamonds with question marks in them or rectangles.
It depends on the font:
- Vollkorn has tofu which are a QR code with the text "vollkorn-typeface.com" below it.
- Roboto is a rectangle with an X in it
- Lato is a rectangle with a question mark in it.
- Noto Sans and Andika have an empty rectangle.
Each appears three times at the start of a paragraph.
-
@Shiny Thanks for actually elaborating on that, I'm surprised that's the case because it seems to imply the text rendering is not falling back to system fonts when glyphs are missing, but instead falling back to the font's error character
-
@chocolatkey said in (New) App Feedback:
@Shiny Thanks for actually elaborating on that, I'm surprised that's the case because it seems to imply the text rendering is not falling back to system fonts when glyphs are missing, but instead falling back to the font's error character
Also weird is that the name for the Noto font is derived from the concept "no more tofu" so if there's one font that ought to work it is that one.
-
Update: https://bugs.chromium.org/p/skia/issues/detail?id=12334 and https://github.com/flutter/flutter/issues/58414
and https://github.com/loic-sharma/flutter-control-characters might indicate it is related to a known flutter issue with tab characters but those examples don't seem to be for Android so it could be unrelated. -
Maybe I have overread it (and I thought I already mentioned it here) but the only problem I have with the app is the reading progress for Manga. Depending on the manga it shows either the green bar if I read it completelly or the blue one even if I finished it. Interestingly the blue bar has different progress lenghts even. So some times I would look like I am in the first third of a book, some times that I am nearly finished.
-
Adjusting margins dont work tried to play it
Also suddenly when changing parts, the scroll view i used change too -
App version 1.1.0 released. Changes include:
- Credits -> Coins on the profile page
- Fix settings changed through "More Settings" button in reader not applying
- Minor improvements to manga image loading speed
- Add download options for manga
- Some bugfixes/improvements
We didn't do anything major for this release because the goal was more to get releases rolling again and a major update of the underlying app framework so we're back to the present version again.
If anyone is lurking here and trying out the new app version already, I'd be interested in knowing how much of an improvement, if any, there is to manga image loading speed.
-
Would it be possible to make it so that we can full control of the text and background colors? I like using dark mode but this new version changed it from white over black to gray over black. The lowered contrast makes it harder to read in normal room lighting.
iOS 15.6.1 on iPhone 13
-
App is now live on Android too
-
@DoomerX It's possible, just will take some work. I would be interested in hearing if anyone else here would like to see this feature. For features like this that increase customizability (which is open-ended) I like to gauge interest.
-
After trying out the new version of the app I can say the bug fixes seem to have made the reader significantly better in paginated mode. It’s no longer unusable and I’ll definitely consider using the app over the site now - though the web reader is still slightly better.
As far as I can tell the only issues remaining in paginated mode are (iOS 15.6, iPad):
- The first line of a new paragraph always seem to have slightly larger linespacing underneath it compared to the following lines. Paginated mode only.
- The first paragraph of a new page still has no indent.
- Splitting of paragraphs between pages is still not ideal (leaving too much whitespace at the bottom of pages), but the current version is probably the best compromise until it gets a proper fix.
- When a paragraph finishes near the bottom of a page, the scrolling range incorrectly allows the user to scroll the text up/down (no text is hidden - I’m assuming the margins or padding is just crossing the bottom edge and making the reader think the user can scroll down to see more text).
- If there is any italics in the last paragraph on a page, the part up until the italics ends is left on that page, and everything after that on the next page.
@chocolatkey said in (New) App Feedback:
@DoomerX It's possible, just will take some work. I would be interested in hearing if anyone else here would like to see this feature. For features like this that increase customizability (which is open-ended) I like to gauge interest.
Personally I’m satisfied with the current brown theme, but I’d definitely support this as having a color scheme I like is my top priority in a reader (along with fonts).
One other thing I’d like is being able to change the line spacing between paragraphs (I prefer less spacing like the web reader).
-
@chocolatkey Not sure if it was intended, but looks like 1.1.0 wasn't pushed to Beta? I was still on beta and stuck on 1.0.0. I had to remove myself from the beta and then 1.1.0 installed.
-
Everything seems to be working just fine, running it on Android 12. Or at least the only issue I have found is the same issue with reading progress on the Releases page not always being correct, especially for manga.
@bfennema said in (New) App Feedback:
@chocolatkey Not sure if it was intended, but looks like 1.1.0 wasn't pushed to Beta? I was still on beta and stuck on 1.0.0. I had to remove myself from the beta and then 1.1.0 installed.
I got 1.10 via Beta this morning... I'm guessing it's because it got pushed after you posted.
