and support for Kbin in all of the Lemmy apps
Very much doubt. I’m sure many will but not all. The API isn’t identical so they’d have to commit to maintaining both.
Yeah I suppose not all of them will want to commit to supporting Kbin, but some definitely will. Honestly though, so long as it’s possible to search for and subscribe to Kbin magazines from Lemmy, that’s all I really care about.
Memmy dev said they plan to as well but “not within this year” if I recall correctly.
It would be great if someone created a fediverse browser native app. Log into all the platforms and add a translation layer to create a truly unique experience. Maybe it would only make sense if you could authenticate one account on all the activitypub platforms? I understand the amount of technical hurdles and maintenance to do so. I suppose I find the thought of experiencing them combined intriguing. If someone created A single app experience, in a intuitive way, I’d definitely give it a try. I can see lemmy posts on mastidon. Would be kind of cool if it could handle that and display those posts using a lemmy ui. But making it seamless.
Based on this: https://codeberg.org/fediverse/delightful-fediverse-clients/src/branch/main/README.md Fedilab, once it supports Lemmy and Kbin
The thing is, when an app does only 1 thing, it’s easy to make sure it does that thing well. It’s going to be a lot of work to support so many different API’s, keep them updated, and provide a good UI/UX.
Yeah. Take the state of game emulation for example. Yes, Retroarch DOES have like 500 emulator “”“cores”“”, all of which can be configured from a single general purpose UI and using a single input layer.
But holy shit does hat UI and input configuration SUCK DONKEY BALLS.
My Anbernic is very happy running 80% of its consoles though it. But I do wish there was something better looking when I have the actual emulation layer running.
I don’t, it’s not that much more work as the basics of it won’t change that much over time and the functionality will be near identical. We might not get newer features that are eventually added though.
I would expect that 99% bits of your app that talk to the API can be the same for both, you just need to maintain slightly different code for interacting with each actual API.
In fact scrolling further through the comments I see that not only is this how @hariette is handling it for Artemis but she’s also looking at making the talking to both APIs bit of the code available to other devs.
