(New) App Feedback
-
Is this for bug-reports, too?
I can't read part 12 of 'These Legs Don't Lie' in page mode on the android app.
I only get a grey reading area, i can't change pages in.
In the endless scroll mode, the part loads.
I'm using a Galaxy S20+ with the latest updates.
already wiped cache and app-data, to see, if that fixed it (did not).. -
@Marius8 I figured out the issue and fixed the part so that it's readable in paginated mode now; we'll work on fixing it so this won't happen for any future parts too!
-
So, on a whim decided to check the app. At the first glance, I would like to be able to sort releases by what I follow and what I don't.
Premium integration. It's kinda weird having to use a separate app for JNC releases.
Library. Sorting options? I'd like to group up books by series, at least.
Table view for Series tab? Some sorting options would be appreciated as well as some function to hide series I don't want to read. Some lists, too? Reading, on hold, dropped, etc.
If it was suggested, I apologise, but these would be my first impressions.
-
@Riaren It's not well-labeled, but you can filter the releases page to followed series only with the star button.
-
@Lisast Thank you. Not a very intuitive design there.
-
Version 2.0.0 is out for Android. iOS will come soon. Changelog summary:
- Add part rentals!
- UI update to Material 3 design
- Add image/request caching
- Bugfixes
-
Curious why manga page count / read% still buggy after so long.
-
@Taedirk iirc it's something to do with their server backend, so requires a significant amount of work to fix, for a relatively minor bug. Just prioritisation of improvements.
-
@Taedirk that's not a problem with the app but the manga backend server itself. An update to that is planned but its part of a bigger step.
-
Would be nice to sort for first releases like how following and catch ups sort.
-
I’m probably about to merely echo something that has already been suggested by others. But since the 2020 release of the app, I’ve found myself increasingly doing more of my JNC prepub and catchup reading through your app than my web browser. One thing in particular that I’ve found that I miss from the web experience, though, is an indicator of when I’ve reached the final part for a volume.
Some viable ways that could be added to the app (in a non-technical sense) might include:
- Editing the displayed title of the part, when shown for users to select a part to read, to include the word “final”. Similar in nature to how it is currently being done in the release calendar on your web page, although the exact implementation could be different in its presentation. Just so long as it is mentioned somehow.
- Adding to the volume’s info panel in the app (that is, what is viewed under: “Series” > [particular series] > [particular volume] > “Info”) the total number of parts scheduled for the volume, allowing users to work out for themselves whether it is the final part of the volume from that information.
- Adding “ghost parts” to the volume’s entry in the app beneath the existing parts, placeholders that get replaced by each completed part as they become available for reading. That would allow users to work it out from context whether the part in question is the final part for that volume based on whether any “ghosts” still remained on the page. (Basically, similar in nature to what currently appears on the series page on the web for each volume.)
- Or perhaps on the blue end-of-part page that appears when you finish reading a part, an extra line could be added that only displays for the final part of the volume. For example, the page as a whole might display “End of [Volume Title] Part # / Back / This is the latest part! / End of [Volume Title]!”, with that last line being the new addition.
If one of these stands out to you as an easy and good option to implement (at some point, time and resources permitting), I’d really appreciate it. I’m not necessarily asking to implement all four possibilities, and if you went for something completely different that served the same purpose, that’d be fine, too. This is just in the vein of “if I could make one change to the app, this is what I would like most”, but ultimately it’s only a matter of some additional convenience in my usage. So no worries either way.
And I understand that some of these ideas might not be changes to the app, but to something else like the server that supplies the parts. Because it’s my usage of the app that motivated me to make the suggestion, I thought this thread might be the best place to make the request. My apologies if I’m mistaken and I should have posted elsewhere.
-
Version 2.0.0 is now out on iOS as well
-
@chocolatkey said in (New) App Feedback:
Version 2.0.0 is now out on iOS as well
Nice to see a couple of the smaller things I previously mentioned fixed.
One new issue I've found is that the gap between the first and second line of new paragraphs in paginated mode is now quite large, for all paragraphs except the first one on a page. I believe I did report something similar before, but back then it was much smaller and barely noticeable compared to what it is now.
It seems to occur for all fonts, font sizes and line spacing settings, but only in paginated mode. Currently using an iPad on iOS 16.3.1.
-
I’ve installed iOS 2.0.1 on my iPhone, and found out that in this version clicking on the Forum menu option will launch a new window in Safari instead of opening a web view in the same app context.
Normally that is fine except that I default to Private browsing mode so all the login info is lost when opening the page in safari. Is there a way to force the app use a normal tab (not private browsing) so that I don’t have to relogin each time?
-
The margin on the new app seems to be off. Now some of the text will end up below the bottom of the screen (iPhone 14 pro)
And can we PLEASE add a +/- button to the margin controls. The slider often moves just 1 or 2 pixels when you life your finger off the slider after you moved it.
-
@anony-mouse99 said in (New) App Feedback:
I’ve installed iOS 2.0.1 on my iPhone, and found out that in this version clicking on the Forum menu option will launch a new window in Safari instead of opening a web view in the same app context.
Normally that is fine except that I default to Private browsing mode so all the login info is lost when opening the page in safari. Is there a way to force the app use a normal tab (not private browsing) so that I don’t have to relogin each time?
Interestingly this problem only arise when selecting forum from the main screen. If I select the forum from a specific book volume it will display the forum inside the app context, which remembers my login information.
From the main forum it will spawn a new browser page in Safari which defaults to private browsing (in my case) that does not remember the login info (as expected for private browsing)
-
Hey all. Just found that there's an app for J-Novel Club. One piece of feedback that immediately comes to mind is some sort of "last read" tracker. Trying to go through one of the catch -up series, and I have to keep guess and checking which of the 25 volumes' parts I was last at...
-
@iacondios said in (New) App Feedback:
Hey all. Just found that there's an app for J-Novel Club. One piece of feedback that immediately comes to mind is some sort of "last read" tracker. Trying to go through one of the catch -up series, and I have to keep guess and checking which of the 25 volumes' parts I was last at...
Isn't there a blue bar that goes across and turns green when you finish the part? Or do you mean you need something at the volume level to tell you which volumes you finished without having to open each one to look at the parts? Okay, yeah, I could see having a box in the corner that says "read" if you've already read every part in the volume when looking at the volume list being useful.
-
@pcj I think we might consider a "continue where you left off" kind of shortcut somewhere which is probably what they are requesting.
-
@daytona yes! Please! Just adding page control with volume keys would make it more comfortable. I would prefer to read/download the advanced release parts locally, but this would be a decent compromise.
