this post was submitted on 18 Sep 2026
28 points (85.0% liked)

Lemmy Apps

7460 readers
13 users here now

A home for discussion of Lemmy apps and tools for all platforms.

RULES:

An extensive list of Lemmy apps is available here:

LemmyApps.com

or lemmyapps.netlify.app

Visit our partner Communities!

Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. !plugins@sh.itjust.works

Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. !lemmy_integrations@lemmy.dbzer0.com

Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. !lemmy_dev@programming.dev

Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. !lemmydev@lemm.ee

founded 3 years ago
MODERATORS
gedaliyah@lemmy.world
Harvey656@lemmy.world
28
Lemonade: Lemmy Client — Open Source (lemmy.world)
submitted 3 days ago* (last edited 2 days ago) by omodasonya2@lemmy.world to c/lemmyapps@lemmy.world
16 comments fedilink hide all child comments
 

Hello everyone. A few days ago, I introduced a new client app here, but due to some concerns about keeping the source code closed and the whole vibe coding thing, it wasn’t exactly well received lol. So today, I’ve decided to open-source it. You can now take a look at the source code yourselves. Hopefully you’ll like it!

Link: https://github.com/datbadaisi/lemonade

Edit: Note: As far as I remember, most of the app was built with Grok 4.5 through Grok Builder. I occasionally used Codex when I ran into difficulties.

top 16 comments
sorted by: hot top controversial new old
[–] Harvey656@lemmy.world 14 points 3 days ago (1 children)

A move in the right direction, has the correct license too. Probably still going to get some upset people over the AI thing, but this is an awesome update. Thank you!

[–] omodasonya2@lemmy.world 8 points 3 days ago

Thank you! I really appreciate that

[–] one_old_coder@piefed.social 14 points 3 days ago (2 children)

You should make small commits next time. Huge commits are bad for reviewing or debugging.

[–] omodasonya2@lemmy.world 9 points 3 days ago (1 children)

Thank you for the feedback. I’ll keep that in mind next time

[–] Zikeji@programming.dev 7 points 3 days ago (1 children)

Check out conventional commits :)

https://www.conventionalcommits.org/en/v1.0.0/

[–] omodasonya2@lemmy.world 4 points 3 days ago

Thanks for the suggestion!

[–] slazer2au@lemmy.world 2 points 2 days ago (1 children)

Its also one of the indicators people use to see if ai was used but not disclosed

[–] one_old_coder@piefed.social 2 points 2 days ago

You're right and I've seen it a few times: first commit is huge, then some small tweaks for the documentation or bug fixing. I'm sad for these people who will never write professionally.

[–] southsamurai@sh.itjust.works 12 points 3 days ago (1 children)

Kudos for handling it well :)

[–] omodasonya2@lemmy.world 8 points 3 days ago

Thank you so much!

[–] BandanaBug@piefed.social 8 points 2 days ago (1 children)

Thank you for open sourcing. That's a step in the right direction. Maybe add a disclaimer that you used AI to vibecode it (and probably which one)

[–] omodasonya2@lemmy.world 4 points 2 days ago (1 children)

Thank you! I’ll add a note about that

[–] BandanaBug@piefed.social 1 points 12 hours ago

I haven't seen the note yet?

[–] IntangibleSloth@lemmy.world 3 points 2 days ago (2 children)

Lemmynade

[–] omodasonya2@lemmy.world 1 points 2 days ago

😂😂😂