cross-posted from: https://lemmy.world/post/1005198
I would assume it is, since the server only needs to serve the API calls and not the whole web site code?
If so, getting people to use the apps could help with the current wave of users a little.
In general the database queries themselves are the most expensive. That and maybe the ActivityPub messages. The HTML/Javascript content from the browser should be nothing in comparison, especially since it’s static. So in the end, it shouldn’t matter if you’re using a mobile client or a browser, assuming both are optimized.
That sounds perfectly logical, but for some reason the site through a web browser has been significantly slower than in an app like Jebora for me.
I haven’t looked at the code for either the web-UI nor Jebora, so I can’t say if either are written optimally. In theory they should be comparable at least because they are written by the same developers, but who knows…
But that’s interesting, for myself on Jebora, it’s slow as molasses. I constantly get network timeouts and JSON errors. On the browser it at least feels smooth, just longer load times.
Nope. The web ui uses something called service worker which caches the html, css and js files on your device and only fetches updates from time to time.
Is that why my browser now takes 100MB more space that can’t be deleted by clearing cache…? I hate that.
What’s the best Lemmy app? Has Christian (Apollo) made one yet?
