this post was submitted on 16 Jul 2023
185 points (97.4% liked)

Lemmy Apps

5552 readers
3 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. [email protected]

Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. [email protected]

Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. [email protected]

Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. [email protected]

founded 2 years ago
MODERATORS
 

Hello! I have made a macOS client for Lemmy - Leomard. It's an initial version of the app, and my first macOS app made for the public.

Features

  • Mac-native client
  • Fast, small and light (only 9.2 MB)
  • Open source (GPLv3)
  • Beautiful responsive interface

Of course, it's a very early version, some features are missing (ex. image uploading), and you may encounter a bug here and there.

Don't forget to follow Leomard's community: [email protected]

Or straight to the project’s Git: https://github.com/Athlon007/Leomard

If you have questions, feel free to ask :)

Hi everybody! This is the initial release of Leomard - a native macOS client app written in Swift using SwiftUI. It’s still in very early phase of development, features are missing, but it’s a start. Feedback is most welcome!

Screenshots:

Changelog

  • Initial Release

Sent from Leomard.___

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago (1 children)

Nice work! I’ve been trying to make a Lemmy app too, so that I could get some SwiftUI practice.

Any tips for working with Lemmy on the backend? The docs have been… not too great for me 😮‍💨

[–] [email protected] 4 points 1 year ago

Trial and error. The documentation and many design choices leave a LOT to be desired.

Such as the way the bearer token in GET request is sent in url param, but for the other requests it’s in the body. Why not just use the freaking Header for that?! Or how the Search request’s search query param is called “s” - it is absolutely not explained what it does or remotely indicated that it’s meant for the query.

But hey, if you want, you could help contributing to Leomard :)