(New) App Feedback
-
@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?
-
The old JNC app now has a message saying it will no longer work soon.
I wanted to restate my hope that the new app will better accommodate text-to-speech. I use the native "Speak Screen" functionality on my iPhone (I used an iPhone 8 for years and now I use an iPhone 13 mini and it works exactly the same). The old JNC app would accommodate TTS perfectly, though if that was by accident or intentional, I'm not sure. When I made sure the prepub was in vertical, I could begin the speaking from anywhere in the prepub with the paragraph I want it to start situated at the top of the screen (I just swipe two fingers from the top of the screen to begin), and it would read all the way to the end of the prepub.
The new app, unfortunately, is not useable for me in its current state when it comes to TTS. When in vertical, it doesn't recognize the on screen text at all ("No speakable content could be found on the screen"). When in horizontal, it will play from beginning to the end of that page, and then stop. Meaning I'd have to restart it after each page flip (in comparison, on the kindle app, it flips the page automatically in horizontal, but I would understand if that's a cryptic or complex feature). I would like the option to choose any paragraph and begin speaking to the very end of the prepub.
I don't know if Apple provides any developer support or info on accommodating my niche request, but I would appreciate if you could look into it :) -
Only thing I'm missing (compared to the web interface) is being able to preview what's going to come out today, as compared to what's already out.
-
I got a message on the app saying that it was the old version so I installed the new version. The new version doesn't work for me. It can't
load user data, new realises list or series list. -
@masterofbeings
In order to do any troubleshooting, they're going to want to know what your device is, the OS version, etc. -
I'm using a Honor 20 Lite, which uses Android operating system. Hmm it seems like it started working earlier, I think the app isn't working for me when using data but is fine with WiFi.
-
@masterofbeings said in (New) App Feedback:
I'm using a Honor 20 Lite, which uses Android operating system. Hmm it seems like it started working earlier, I think the app isn't working for me when using data but is fine with WiFi.
If it were a data vs WiFi thing, I'd suspect lag issues in re stuff timing out?
For the real troubleshooters, rather than wiseacres like myself, the version of Android would become pertinent. -
@weasalopes
My phone tells me that it is android version 10 -
@masterofbeings said in (New) App Feedback:
@weasalopes
My phone tells me that it is android version 10Mine's Android 11, with no problems with the app.
But Android 10 is still pretty recent as these things go; September 2019 release.
Probably not the issue, but I'm not an app developer so take that with a large grain of salt. -
Now that I'm back home, I can confirm that the app fails to load stuff when using data. It gives this message on the release tab: "Failed loading releases: No response received from server - SocketExpection: Read failed (OS Error: Connection reset by peer, errno = 104), address = labs.j-novel.club,port = 52286"
And a similar message on the series tab. The account tab just says "Failed loading user data from server" -
@masterofbeings
OK.
Now there should be enough info for the JNC Support guys to have a clue.Well, verifying terminology just to be sure, since I'm an old fart and late adapter in regard to mobile computing of the non-PC/Laptop type...
When you say 'data', this is your phone's cell connection, yes?
I suppose in this day and age info in regard to what cell transmission type (4G, 5G, etc.) would become relevant to the situation if it is a 'timing out' problem.
Just had a thought; this is the feedback topic.
I have a vague recollection of there being a Support topic concerning the app as well, and that's probably the one the support chaps monitor...Gathering together all the info from our various posts here and summarizing that in the proper support topic might be an idea.
Or at least checking to see if my memory isn't faulty this time around. -
@masterofbeings This sounds to me like your cellphone internet provider isn't letting you access
labs.j-novel.club:52286for some reason. The only workaround I can think of, short of changing providers or shouting at them, would be for JNC to update the app to use port 80/443 for this. I'm sure they have their reasons for using a different port, however. I'm just one more person speculating here, so I don't know. -
@nosgoroth said in (New) App Feedback:
@masterofbeings This sounds to me like your cellphone internet provider isn't letting you access
labs.j-novel.club:52286for some reason. The only workaround I can think of, short of changing providers or shouting at them, would be for JNC to update the app to use port 80/443 for this. I'm sure they have their reasons for using a different port, however. I'm just one more person speculating here, so I don't know.I hadn't considered that WiFi would link through their 'traditional' ISP while Data would link through their Cell Provider, adding the possibility that the Cell Provider might be 'doing something weird' distinct from anything related to the individual's device and J-Novel Club. My realizing there would be a different rate of data transmission has nothing to do with this.
That's an aspect of things I've no background knowledge concerning, no real grasp of the possibilities for said third party 'futzing things up'.
-
@weasalopes It wouldn't be the first time I see mobile ISPs running connections through weird proxies and messing up perfectly valid requests. At work we had to deal with an issue that only happened to users with a particular phone company, and all we could do was throw our hands up and wait for them to fix it.
The main reason I think the mobile ISP might be the issue is that, if I'm interpreting that error message correctly, this request is using a weird port. Now, that doesn't mean there's anything bad about it, but it's something that can cause problems sometimes, like when a public university wifi blocks nonstandard ports for extra security (standard ports being 80 for HTTP, 443 for HTTPS, 20-22 for FTP...), so if the error only happens in a particular network...
Just a load of speculation, though.
-
Small UX thing, the part drop down list includes parts i don't have access to. This is the drop down when clicking the header while reading a part. If I select one of them, I get an access denied error (as I would expect).
Side note, any thoughts on open sourcing the app? The app itself isn't j novel clubs key differentiator (that's the novels and prepub access), and is expect the main app users are the kinds of rabid fans that might contribute.
-
@nosgoroth That is sort of incorrect, the port you're seeing in that message is the outgoing port from the device. The requests being made are using HTTP/2 over TLS on port 443 (HTTPS).
