We do plan to integrate the translation API, but it might come after we release 2.0 to the App Store—our primary focus right now is reaching feature parity with the v1 app so we can ship 2.0. That being said, we may build it into 2.0 before then as an excuse to play around with the new API.

Thanks for the bug report! If you tap the error message at the top of the screen it will give you a more detailed error message—would you mind sharing that message so we can debug further?

Glad you like it!

The shadow around those elements is intentional–the SwiftUI component that renders those elements has extremely limited styling options, and so can’t take the nice rounded border. The shadow is there to provide visual distinction against the background.

Thank you! We’re lucky to have such a great community–all your feedback means the world to us.

Autoplay is planned–forgot to add it to the planned features. It’ll likely be iOS18 only.

Pure black is also in the works.

Yes! You can join the weekly beta, which gets an automatic build every Friday, or the stable beta, which gets more polished updates as we complete development cycles.

This issue should be fixed in the new 1.3.7 release.

Thanks for the bug report! We’ve already merged the mark read on scroll fix. The sound issue has proven a lot harder to track down, but we’re working on it.

1.3.6 has just released to the App Store–it should resolve this issue.

Thanks for the feedback! We’ve received a couple requests for an oled/“blackout” theme–we’ll have one out soon.

Are you on iOS 18? There is a known issue where swipe gestures and scroll gestures conflict on iOS 18, which causes the behavior you describe. We have a fix currently in app review that should be live shortly.

Thanks for the bug report! We’ll look into it.

Thanks for the bug report! Are you on Mlem 1.3 or the 2.0 beta?

To add a little more insight on the gifs side: video handling is the next major item I’m working on. In theory, the media framework we use should make gifs free once video handling is working, so hopefully they’ll be coming soon.

Thanks for the feature request! I’ve opened an issue to track it.

We don’t have a preference–we monitor both pretty actively so whatever is easiest.

Thanks for the bug report! It looks like this is due to the antique backend Beehaw is still running–we’ll have a compatibility patch out soon.

Thanks for the bug report! We’re working on it.

Thank you!

Haptic feedbacks aren’t in the current build, but we’ll have them in the next! That build should ship tomorrow.

Is there a way to preserve settings from the old version to the new?

Not right now. We’ve rewritten and reorganized the entire infrastructure that handles settings and configuration, and the new and old schemas are more or less alien. We’ve got an issue open to build a settings import/export tool which will allow things like easily migrating settings across platforms that should also make this possible.