If you want to keep using Mlem while the TestFlight is down, you can just download it from the App Store–the current release build is identical to the TestFlight, and should keep all your preferences.

Should be pretty straightforward, we’ll look into it for 2.0

TL;DR: Mlem v1 is not fast; Mlem 2.0 (announcements coming soon!) will be.

We’re aware of a number of performance issues with the current codebase, which all together result in the app not behaving as responsively as we’d like. Unfortunately these are largely due to design choices made during the hectic sprint to App Store release last summer, and so are infeasible to fix without rewriting the app from the ground up—which is why that’s precisely what we’re doing. Our 2.0 build should be significantly faster; we’ll have some announcements about that in the near future.

Sure! One of the big things we’re reworking for 2.0 is how we handle accounts, which includes changing the format of how we persist account information. The compatibility changes in this build add extra decoding logic to the account persistence system so that both v1 and v2 can load a saved account regardless of which version saved it.

1. Yes! We aren’t happy with the current state of our media viewer. 2.0 is a backend-focused rewrite, so probably won’t have a new media viewer on launch, but it’s without a doubt high on our list of important features.
2. Hard to say. Our iOS compatibility policy guarantees compatibility until iOS18 reaches 75% market share; after that, I can’t make any promises. We take the decision to drop compatibility very seriously, and try to only do so when the features offered by the newer iOS are valuable enough that we would be compromising the potential quality of the app by ignoring them.
3. Yes. We’re still working out some UX concerns stemming from the fact that it’s very slow to search posts and comments compared to communities, but it’s in the plans.

Progressing well! We’re hoping to have the next TestFlight build out soon.

That’s unfortunately not currently supported by the Lemmy backend. There is an issue open for it, though it doesn’t appear particularly active right now.

We have some major changes in development that might make this feasible to implement client-side–I’ve put up an issue for it, but can’t make any promises pending a more thorough technical investigation.