this post was submitted on 01 Aug 2023
15 points (89.5% liked)

Jerboa

10135 readers
11 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
 

So, past few days, the instance I have my account in, seems to crash and burn every morning, when I would like to browse it. I wouldn't otherwise mind waiting fir the few minutes it takes to the issue being fixed, but Jerbia decides it's a great idea to PURGE EVERYTHING if there is any sort of hitch in the login.

Now, I do notice I get a some sort of javascript error every time this happens, and I suppose it's a null reference error, but I also imagine the issue is not isolated to a situation where the instance itself is down, but can probably be replicated by a local network outage. And an easy solytion is to add a variable that tells the app that the logins used has been valit, with an option to change the password, rather than just lose everything. Zure, it might be cool if there was a tiny check to see if the instance exist, when loging in with a saved credentials, and notify about not being able to reach it, but the most important feature would be to have a "newly invalid login" to still exists within the app.

[EDIT]: To clarify: even if the logins on the app would still be there after the instance comes back up and the app has been restarted, the issue still presists, because there is no excuse for displaying the credentials as forgotten, and defaulting to anonymous, where you could simply display an error that implies the logins are still ther, but not reachable. Tint the username red, and add [login error] at the namespace. Or better yet, add a tiny ⚠️ icon in front of the handle, that will provide information aboit the error.

I am not looking how to solve this for myself, I am reporting a bug/oversight that will affect peoples retention rate with not just Jerboa, but with Lemmy as a whole. Now, I know Jerboa isn't the only client out there, but I'd rather see it get better than try and find an alternative, but if the welcome for suggesting an improvement is "it's not really a problem to me, so I don't even care if it's a good suggestion, you should just get over it too", I'm rather tempted to jump ship if an alternative pops up.

While some people might consider this "just a quality of life thing, L2B, noob", I'd say this is one of the things why open source centric apps rarely take off properly: the UX sucks because it's dismissed as "unimportant, because I coded it, and I know how to use it and whst it does under the hood".

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

I created a second account to work around this and it works, but that's less than ideal.

[–] [email protected] 2 points 1 year ago

I fixed the problem already, dessalines just needs to cut a release