this post was submitted on 11 Dec 2023
73 points (100.0% liked)

/kbin meta

200 readers
2 users here now

Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign

founded 1 year ago
73
submitted 11 months ago* (last edited 11 months ago) by jwr1@kbin.social to c/kbinMeta@kbin.social
 

I've been working for the past week on a new kbin app. At the moment, it's just a prototype and only the "Feed" view has content (you can't sign into an account or post anything yet); you can see threads, thread images, thread comments, thread links, and thread votes/boosts. You can also change the "Theme Mode" and "Instance Host" in the settings.

Here's a link to the source code (contributions welcome for those that know flutter): github.com/jwr1/interstellar.
For testers, here's the link to the latest working build: github.com/jwr1/interstellar/releases (AppImage and APK).

Feel free to post any bugs or suggestions in the comments, on GitHub, or on the Interstellar magazine.

Again, this is just a prototype. If someone else is working on a better kbin app, I might just use that instead.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] DarkThoughts@kbin.social 3 points 11 months ago (1 children)

I think he said even further back that he wanted to eventually come back to it but I also certainly did not wanted to discourage OP from working on his own one, especially an open source one that could get picked up by someone else if needed. I think the more apps we got, the better. And hopefully some of the Lemmy exclusive apps will support kbin too after the full API release.

[โ€“] ernest@kbin.social 15 points 11 months ago* (last edited 11 months ago)

My priority is definitely the development of kbin-core, especially now that work on the app has started. For now, I prefer to focus my attention on adapting the API to the latest features. It may turn out to be necessary sooner than expected ;)