Mlem: An Open-Source Lemmy Client for iPhone and iPad

Mlem is a native iPhone and iPad app for reading and joining conversations on Lemmy, a network of independently run discussion communities. It is a client for that network—not a social network or server of its own.

The current App Store version is 2.6.0 (checked 2026-10-01). Recent changes focus on inbox handling, the post and comment composer, and the actions you use while browsing, rather than trying to reinvent the familiar discussion-feed pattern.

Mlem is a client for a network of communities

Lemmy is federated: separate servers, often called instances, host accounts and communities while exchanging eligible public discussions with one another. Mlem gives you a mobile interface to that network; it does not operate the servers or decide their moderation rules.

That separation is the main idea and the main extra bit of context. You get more than one central feed to choose from, but availability, local rules, moderation, and service reliability depend on the instance and community you visit.

Your instance is part of your account

Before signing in, choose an instance whose registration policy and community rules make sense to you. Your account belongs to that server, even though it can interact with communities hosted elsewhere on the network.

This is not quite the same as creating an account with one global provider and seeing every post in one universal timeline. Search and community discovery can feel less centralized, and individual instances may have different policies or availability.

A familiar flow for feeds and discussions

Once connected, the everyday loop is recognizable: browse a feed, open a post, read its replies, vote, and join the discussion. Communities give topics a home, while the network lets people on different instances take part where federation allows it.

Mlem is most interesting if you already use Lemmy or want to try it from a phone without treating the mobile browser as your main interface. The instance model is worth understanding first; the client cannot make the network's separate communities behave like one centrally managed service.

The project is written in Swift and SwiftUI, and its source is public on GitHub. That makes it useful to evaluate both as an end-user app and as a concrete open-source iOS client.

Version 2.6.0 smooths out inbox and composing

The latest App Store release adds more control around the inbox: visited items can be marked read, and settings cover automatic refresh and mark-as-read behavior. Message swipe actions also make common inbox tasks quicker to reach.

For writing, the post and comment composer can offer a language picker when your account has more than one discussion language. The release also expands the interaction-bar editor and includes moderation, PieFed, and stability updates; the store listing has the full change log.

Put the actions you use within reach

The interaction-bar editor is a small but practical sign that Mlem is being shaped around repeated use, not only around a feature checklist. You can adjust which actions appear there, while message swipe actions keep inbox work close to the item being handled.

These are workflow refinements rather than a promise that every community or server behaves identically. The available content and moderation decisions still come from the Lemmy services you use.

Read the privacy label in context

The App Store privacy section says “Data Not Collected.” Apple notes that these disclosures are supplied by the developer and are not verified by Apple, so treat the label as a developer declaration rather than an independent audit.

Using a Lemmy client still involves sending account and interaction requests to your chosen instance. Public posts can be federated, and each server operator sets its own policies and logs; the store label should not be read as a promise of anonymity or as meaning that no network service receives data.

If privacy is a deciding factor, read the policy of your home instance as well as the app's store disclosure. The server you choose is part of the trust decision.

Check the current device requirements

The current App Store listing requires iOS 26 or later and iPadOS 26 or later. The repository README still mentions iOS 18+, so there is a documentation mismatch: for installing the current store build, use the App Store compatibility information as the operative requirement.

Apple's compatibility section also lists Apple silicon Macs and visionOS, but marks Mlem as designed for iPad and not verified for macOS. Treat iPhone and iPad as the documented experience; the listing is not evidence of a separately tested native Mac client.

The App Store lists English and French. Check the listing on your device for current regional availability and compatibility before installing.

Install Mlem from the official App Store

The project has a current App Store listing, so most people can install the ready-to-use app directly—there is no need to build from source just to try it. Open Mlem for Lemmy on the App Store to check availability for your Apple account and device.

open 'https://apps.apple.com/us/app/mlem-for-lemmy/id6450543782'

GPL-3.0 source, with separate asset attribution

The repository licenses Mlem's app code under GPL-3.0 with an App Store compliance addendum. The README also credits a third-party Beehaw community icon under CC-BY-NC-SA 4.0; that asset attribution is separate from the app-code license.

Should you try Mlem?

Mlem is a good fit if you want a native iPhone or iPad way into Lemmy, value an actively updated open-source client, and are comfortable choosing an instance rather than expecting one central service to set every rule.

Start with the App Store listing and your chosen instance's policies. Keep in mind the current iOS 26 requirement and the limits of the privacy disclosure; if those fit your setup, Mlem offers a polished mobile front end for a more distributed style of online discussion.

# Open the official App Store listing:
open 'https://apps.apple.com/us/app/mlem-for-lemmy/id6450543782'