My #1 choice for web client, amazing
nostr:note1qqkevx9y8zywy4h06h2ntx7vy304d7sdc42xfn4xszvt2l9e4qwq895ykr
Discussion
People's most favorite client changes every 3 months. Next will be dev.nosotros.app
Replying from it now, not there yet in terms of UX, not well thought out IMHO. More hoops to jump through
Sure, lots to do yet. But the I like the UI choices more then jumble's. By far.
As far as the speed and intuitive navigation concerned, Jumble is hands down the winner. Smooth as butter, no pending UI hanging forever when there are no notes or other crap that is being loaded, attention to details. I’ve tested 90% of clients I could find and all of them had some sort of obscenities or UX issues. Even basic button click, and immediate show of pending UI is absent on majority. Performance is another area, where bloated clients are taking multiple seconds to load anything. Some do not even have a way to login (in obvious way) while asking you to log in. It is sad show from my testing.
I really wish I could understand, maybe you are using a very different client that the one I made it, after I rebuild a lot of things with sqlite for caching, I barely see any loading screen once things were already cached, but let me know anything I could do to improve nonetheless.
https://blossom.nosotros.app/0767153234057d35ca7acc9cf893cdfd9b2aadc68360e63813a0a5a67b234c28.mp4
Speed is not the only thing that matters, it is all about perception. I suggest to take a look at jumble.social and not basic navigation, how loading is done, see how they perform refresh (pull down on notifications does not engage default browser refresh, instead it does the app driven refresh), pending UI is smooth and does not shift layout left or right or up/down, and many more details to make it feel fast and smooth.
The sqlite caching looks great! I’d love to optimize it that way too, but I’m a bit worried I might not handle the cache update logic properly.
Nope
I do not understand web client. Can someone ‘splain?