this post was submitted on 08 Mar 2025
172 points (98.3% liked)
Mlem for Lemmy
5379 readers
31 users here now
Official community for Mlem, a free and open-source iOS Lemmy client.
Rules
- Keep it civil.
- This is a forum for discussion about Mlem. We welcome a degree of general chatter, but anything not related to Mlem may be removed at moderator discretion. This is not a forum for iPhone/Android debate. Posts and comments saying nothing but "iOS bad/I use Android" will be removed as off-topic.
- We welcome constructive criticism, but ask that it be both precise and polite.
FAQ
- When will insert feature here be implemented?
- Check our issue board--if there isn't an issue open for the feature you want, feel free to open an issue or make post! Just remember that devs are people too--we're doing this for free in our spare time, and building a quality app takes a lot of patient work.
- Is Mlem available for Android?
- No. Mlem is written using SwiftUI, which is not currently supported on Android. If such support becomes available, we will look into bringing Mlem to our Android friends.
- How do I join the beta?
- How do I join the dev team?
- Head over to our recruitment channel, or go straight to our GitHub and read CONTRIBUTING.md to get started.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Really like the new design and I think Mlem definitely carries the same "native" feel that Apollo used to. I just wish it had customizable swipes so I could make the switch from Voyager, but it looks like that's a low priority feature for now
Thanks for the feedback! This has a been a highly requested feature for a while. It would have been tricky to implement in Mlem 1.0 due to the app’s original design. However, in Mlem 2.0, we’ve built the swipe actions system with future customization in mind. We're planning to add customizable swipe actions sometime soon - the GitHub issue is here, if you want to keep an eye on our progress :)
That's great to hear! I saw the issue a few days ago but since it didn't have any comments or milestones (at the time) I assumed it was just lost in the backlog. Thanks for the update! :)