Can't really make apps for a site that doesn't have an API. They did announce recently that Kbin's API is nearly done, so soon there'll be a flood of Kbin apps as well, and support for Kbin in all of the Lemmy apps too
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.
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.
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.
This is why Lemmy's tangential features, such as being able to post from Mastodon accounts, or being able to post to that video service, are also not going to happen any time soon. It's just a lot of moving pieces, for functionality that's more interesting than useful.
You can install the kbin interface as a PWA on mobile, and it works pretty well. There are some kinks for sure, but it's 100% usable and better than lemmy.
I was thinking of making my first attempt at an android app a kbin app because of the lack of options, but their documentation (while done really well so far) isn't fleshed out yet.
Lemmy's Documentation is very confusing to me as someone still learning to program (does it get better when you are more experienced???), but it's definitely a lot more fleshed out, so that's why I'm attempting to make just another Lemmy client looool
Hi, currently three years into a job title that indicates I program for a living (it sounds more like I'm a manager). I do Python professionally and work on learning C. It... it kinds gets worse, if you go this far, but you're more able to handle it.
It's not 3rd party app developers fault that kbin didn't have any stable api yet. Now that they fast track the api development, I think we can expect more 3rd party apps coming soon.
I'm about to launch a Lemmy app (by Monday, my friend yelled at me when he found out I'd been using it exclusively for weeks without putting up a beta), and kbin support is on my to-do list.
Frankly, I started using Lemmy, saw this could be the thing I've been waiting for, and decided the edges were too rough. So I made the app I always wanted for Reddit with the goal of using multiple servers, multiple accounts seamlessly. My guiding philosophy is making the client into another layer of federation,
I checked out the kbin docs and I can probably knock it out in a couple days, I've got abstraction layers to handle different versions and forks of Lemmy... Head over to [email protected] and let me know this is something people want and I'll put it higher on the priority list
Artemis developer said they're gonna public source the code soonand their app supports both Lemmy and Kbin, which might help you with Kbin support. Just a suggestion, I know nothing about how code works, though.
If you add support for kbin, you'll probably going to add support for kbin's microblogging feature. If you added support for kbin's microblogging, might as well add mastodon support. Heck, might as well add pixelfed support to the mix, why not? Voila, now you have a super federated app.
Whoever ends up doing so should set up the interface so that Lemmy posts are blue and kbin posts green, that way Lemmy users can downvote us and call us poor.
You could hack that into most lemmy clients right now, with either a manual kbin list or one automatically populated by querying the instances api directly.
I recommend forking liftoff and calling it lMessage, l for liftoff or lemmy, and message because now you can message all those pesky kbin users that they should bin their kbin and join a real instance
personally it is kinda superior to Jerboa, since it has a feature that is my favourite: keyword filter, but also i can browse instances that can be defederated from each other, all the fediverse in one app: could even browse hexbear.net (which is not federated with anyone yet), kbin.social, ..all on the app (and can browse instances as a guest without an account, which makes things way eaiser. unlimited block list. no bugs. it was suggested to me and i keep suggesting it for others since i didnt regret using it.
Working hard on it! Can’t wait for API to go live to make it widely available.
I wrote an API adapter layer to be able to support both kbin and lemmy in the app. Want to open source that as a package, so hopefully more apps can easily add support for both 🤞
For me it's mostly just that it supports kbin and the design because I never got to use Apollo as an android user, and it's supposed to be at least extremely similar design wise (from what I've heard)
There are plenty of rough edges that apps are able to buff out that a browser cannot.
I use plenty of things in a browser, but if I'm gonna scroll something daily... I want that image viewer with tap slide zoom. I want that specific folder that the app saves shit to instead of just "downloads". etc. etc.
Having a dedicated app is just more convenient in most cases. And apps generally offer more features and QoL improvements compared to a site. After using memmy for about a month I can’t use the official site, especially on mobile.