I think there was a kbin API and Ernest pulled it because he wanted to improve it. I think time will show that was a smart move. App developers need the API to be stable & unchanging; kbin can likely see how the Lemmy API is used by Apps, learn and improve from this.
We do know a new improved API is in the pipeline, and I agree with z2k, Apps will follow soon after.
Lemmy is also a lot older than kbin - kbin is only a month or two old, iirc, and it’s still technically in beta. I’m sure once an API of out for it, we’ll start seeing a lot of apps popping up. It just takes time - we’ve only just in the last few months seen a boom in quality Mastodon apps.
I’d say that in about six months, we’ll be spoiled for choice.
PWAs always feel way clunkier than a proper native iOS app.
I fully believe the reason Apollo was the best Reddit app, period, is because it was 100% native and fully embraced all the design patterns used throughout the rest of iOS. No amount of flashy CSS or fancy javascript frameworks can fully re-create that level of cohesion.
Yeah I have the pwa on safari / iOS . Fine for the most part , but I seem to struggle with navigating. The browser back button seems to be unavailable a lot
Having the option of native clients, whether on desktop or mobile, is good. Having a mobile app that fully respects its platform's design language or a desktop client that uses less resources than a web browser and will run without issue on something like a Pi can go a long way to making a web platform enjoyable to use.
Hell, you could tweet from a BBS at one point (maybe you still can?) and until July 1st you can browse Reddit in a Linux terminal using basically zero resources. Lemmy has this neat project for a web interface that will run on a toaster, for example. Maybe kbin will get something similar once its API is mature.
I think kbin is awesome. I also think a major drawback to kbin is the lack of a working app. I understand that this has to do with an API or lack thereof. It's still a drawback.