On desktop kbin is 5x better than vanilla lemmy.
But on mobile I have several FLOSS lemmy clients. They all have their pros n cons. Their development is spread out with different projects. Work and the responsibility are distributed from the main lemmy maintainers.
The kbin webapp is pretty good, but not as good as a native client. There is of course only one.
My feeling is that designing for clients (having an API) imposes some kind of discipline on projects. Like you can’t just do whatever willy nilly.
My other feeling is that kbin is setting up to be like iCloud whereas lemmy is more akin to sftp.
Thoughts?
There are a lot of technical (PHP vs. Rust) and user experience (UX) differences, but I don’t understand the comparison. They may have various approaches to AP implementation, but ultimately, they are both AP aggregators. Of course, that doesn’t take into account the political concerns surrounding Lemmy’s codebase. mini crossword