this post was submitted on 19 Aug 2025
17 points (100.0% liked)
Mlem for Lemmy
6250 readers
2 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This would be cool.
I did look into implementing something similar to this in the past, but there are some tricky UX problems associated with this design. Most prominently: if a user taps on a community link in a comment, what do we do? The intuitive option would be to slide a new page over both the sidebar and content panes, but unfortunately iOS only allows us to slide new pages over the rightmost pane. I might take a look at how Narwhal handles that 🤔
At the moment, we are focusing on implementing support for iOS 26, and following that we’ll be working on support for Lemmy 1.0. I’d love to revisit this at some point, but we can’t make any promises on when that might happen.
We’re open to contributions if anyone is interested in implementing something like this :)