this post was submitted on 26 Jun 2023
29 points (96.8% liked)

Jerboa

10298 readers
1 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
dessalines@lemmy.ml
29
Lag/Stutter when scrolling thru posts. (partizle.com)
submitted 1 year ago* (last edited 1 year ago) by partizletestthine@partizle.com to c/jerboa@lemmy.ml
14 comments fedilink hide all child comments
 

The entire app doesnt feel "smooth" everything is alright but scrolling is a nightmare. I'm wondering if everyone is experiencing this or just me? Using a Samsung a04.

EDIT: The website is perfectly fine no lags or stutters. I don't think it's an issue with too many people since opening posts and loading images are instant its the scrolling that seems too lag

EDIT 2: https://github.com/dessalines/jerboa/issues/445 Found this in git

you are viewing a single comment's thread
view the rest of the comments
[โ€“] thetreesaysbark@sh.itjust.works 1 points 1 year ago (1 children)

Okay.

But the UI scrolling shouldnt be affected by the server being hit by many requests imo. The only way I could see an impact is if the UI waits for something to load before allowing it to be scrolled in to view - but I'm no front end (app) dev. I did work on a content serving project as a full stack though, except that was a few years ago and browser based and only vanilla js and html on the front end. Still, scrolling issues were not impacted by content serving latency as it was easy to plug dummy tiles in until the server gave its content.

The hotdog analogy doesn't make sense to me as that would be a Lemmy instance (all content serving server) latency issue, not a jerboah app UI component issue?

Spreading out over multiple instances is one option to reduce content serving latency, but it would also be interesting to see if a single instance can be distributed over multiple servers - I'm not sure of the lemmy capabilities at the moment though.

[โ€“] Bread@sh.itjust.works 2 points 1 year ago

My guess is that that the UI is waiting for something from the server that hosts the user and therefore the content. That is more or less what I meant with my analogy. Keep in mind that I don't know this for certain, I am just going off of things that I have heard about how the fediverse works. If a developer for the app or lemmy can weigh in for a more complete answer, that would be great. I could be completely wrong for all I know and am open to knowing more.

If single instances become large enough, finding a way to split those up may be necessary if you can't just improve it by getting better hardware or optimizing lemmy to run better. I guess we see what becomes necessary.