(New) App Feedback
-
Until now whenever I opened a new chapter, first page had HUGE BOLD CHARACTERS (like size 36 when the normal size should be 12).
Since yesterday chars have the right size.
-
On the latest iOS TestFlight beta, whenever I go to the next part at the end of a part from within the reader, the releases page will not update the progress properly for those parts after exiting from the reader.
In addition, if after finishing e.g. Part 1 and Part 2 and then returning to the Releases page, and then, when re-entering into Part 1 or Part 2, it will reset the read progress to 0 and lose track of the actual progress/ completion status.
-
Thank you for your hard work on the app! Hoping that v1.0 solves the remaining glitches with horizontal reading.
For the future, I've a couple of requests:
Feature request: keep track of read parts
Unless you're quite disciplined, if you're reading many series chances are that you may not be up-to-date with all of them. For example, I may have read a part half way through before doing something else, and forgot to read the rest.
Currently on the beta app, you can long tap on the part (which I just learnt about) allowing you to go to the volume and look at your progress for the other parts in the corresponding volume, but it's still a few taps away, and requires more steps if you want to look at previous volumes.
For my web app, I'm having all parts showing horizontally, which I think it fits better. I've a demo at the bottom.
Feature request: show upcoming parts
And to know which parts are coming up and when, it would be nice to also having them showing in the app. The demo also shows this.
Demo: https://imgur.com/x3bqEdB
I do like how I managed to get these features, but there may be more appropiate approaches. (I admit I'm being quite heavy on the API.)
Quof got a break.
WHAT'S THE STORY WITH THAT FREAKING BLACK DRAGON?! -
@crimson-wise A lot of the background work needed for these features is going to come with a new backend, so it will take a bit. We are going to be getting rid of events entirely for example and replacing them with unavailable parts and other metadata.
-
@chocolatkey Happy already to know there is interest. Thank you for your work, and congratulations for the v1 release!
-
This post is deleted! -
@chocolatkey, I just saw that the app went official as 1.0 on the Apple app store. Thanks for all your hard work!
-
This post is deleted! -
@piisfun if you're in the beta program, I think it'll still call it a beta. I think they have to release it on both the production and beta channels for the people who are on beta to actually see it. Otherwise you'd have to leave the beta program to get the release version.
-
I just tried out v1.0, and honestly I’m quite disappointed in the lack of progress on the reader. Seems like it has regressed from where it was at in v0.3 (before later updates made paginated mode unusable). This is all taken from the perspective of paginated mode on an iPad, which I know is still being worked, but a number of these issues are contained in both. A lot of my issues are personal preference, so it would be nice to see more settings for customisations.
- I’m not a fan of the new spacing between paragraphs. Definitely prefer the web reader with little/no additional spacing. Would be nice to be able to customise or disable this.
- Indent size. Not a major issue, but would still be nice to be able to customise it to make it a but smaller/larger.
- There seems to be additional line spacing between the first and second line of a new paragraph compared to following lines.
- General issues like the first paragraph of a page not being indented in paginated mode, and margins not working at all.
It may seem like I’m nitpicking, but all of these points work perfectly in the current web reader on the same device. I’ve been wanting to move to the app because I really like the app UI and navigation, and I’m tired of the web reader not saving settings between sessions, but the reader is still the most important part for me so I’ll be holding out for future updates.
-
more or less just thoughts on JNovelClubApp for the reading based on some stuff inside moon reader - Epub app.
-
When reading a book there could be a dark bar at the bottom or the top where you can tell the time and battery life of the device that would be super nice to have and convenient.
-
RGB Text being able to change the text colors would be super nice, I prefer to read in the color orange not sure why but it really feels comfortable in the color orange lol.
more or less I think I'm just being picky like most others as well, it is usable from my point of view, though the text is quite small when doing left and right page-turning, which isn't really a big issue since there is scrolling instead
-
-
When reading with the black theme on and white letters, the letters are too bright even at minimum illumination setting at my device, so I hope you are either planning to implement a brightness slider into the app itself, or otherwise decrease the defaut illumination of white letters on a black background.
-
Just wanted to hop in and thank everyone for their feedback! While we may not be able to make updates as frequently as some would prefer, we do review all the suggestions and try to make improvements where we can. Thank you for trying or using our app!
-
I'm trying to read the new Bibliophile Princess manga chapter, and I can't get it to load. The TOC loads okay but then it just sits and spins forever trying to load page 1. Tried a few other releases at random with the same results, only with manga though. Light Novels are still loading fine. Galaxy Tab S2 on Android 7 with the 1.0 version of the J-Novel Club app.
-
@pcj so I finally got it to load... it's still horribly slow. But I also noticed that Bibliophile Princess vol 5 chapter 6 isn't marking completed once I finish it. It says the progress is 28/32 pages, but there are only 28 pages available, so I don't know if there's 4 pages missing or if the count is just wrong.
-
@pcj I've fixed the progress issue, that's due to the stopgap solution that's currently in place to count the total amount of pages in the backend, where if the wrong number of pages is uploaded first in our backend, the page count stays wrong.
As for the loading speed, I'm not sure why that is happening. Manga loading is slower than I'd like it to be, taking 2-3s for initial chapter load, but after that, unless you are really speedreading a chapter, the loading speed should be more than sufficient. Is there any other bit of info specific to your situation that you think would help?
-
@chocolatkey it's working great right now, so whatever was happening isn't anymore. At the time it was taking 15 to 20 seconds per page to load, if it loaded at all. But only for the images. TOC loaded quick and so did chapter indexes.
-
Android app doesn't have manga section like iOS does. Is there a reason?
-
@striven on android if you hit the search button, there's radio buttons for All/Novels/Manga at the bottom, and it switches the whole view instantly when you hit them.
-
@striven Unless you've intentionally filtered out manga, I'm not sure what you mean. Could you elaborate?
