(New) App Feedback
-
@weasalopes Well I suppose that makes sense, the topic reads more like a here's what we fixed in the last month announcement, not a development roadmap and feature request topic.
-
I wish the app had a reading history section. Preferably one where you could easily navigate to the last part you read, as soon as possible after opening the app.
There used to be a feature that when you closed the app and reopened it, a popup asks if you want to continue where you left off. Now you have to either scroll down your releases tab until you find the part that's partially read, or query the title in the series tab and navigate to the correct part. It's a bigger hassle than it needs to be imo.
-
Coin totals do not show up in the iOS App
Since the changeover to coins instead of credits, the iOS app do not reflect the amount of coins available. I'm on the latest version from the Appstore (iOS 15.5)
-
@anony-mouse99 Yes, that's because the latest update is from a while ago, before coins were a thing. Once the new update is out, you'll see coins
-
Is there a planned fix for the inability to mark manga chapters as done/read? Or the fact that several of them can't be completed at all because the app says there's more pages in each chapter than there actually are? (For the latter, AoaB 2x6 seems to be the most obvious example).
-
@mystyk It's a bigger problem than just the app. This problem should automatically be fixed once we finish migrating to our new backend.
-
I don't know if it's only me, but manga pages load so SLOW, it's really vexing, and changing the quality doesn't show any improvement whatsoever.
It would be nice if this gets improved as I love using the app to read my series.
BTW, I have a phone with Android 12.Thanks
-
@lucascba Would it be possible to send us a screen recording of this to support@j-novel.club ?
-
Ok so a few things I found while using the app:
-
Mangas take forever to load. Would be nice if I could make them auto download when they get published.
-
Why does it ask me if I wanna open the volume when I press and hold? Why else would I do that?
-
There should be a way to get from viewing the parts of a Volume to viewing the Volumes of a series. Perhaps the back button could instead of going to releases to that.
-
It would be great for us non English speaking folks to be able to quickly translate a word or sentence. Like honestly, Athletes foot? Just call it what it is: Foot fungus.
Thanks for coming to my ted talk and keep up the good work!
-
-
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.
