This is intended behavior—instance admins can manually change account creation dates in the database, including to dates in the future, which leads to some funny account ages. We plan to implement some custom handling for these cases, but since they’re quite rare it’s not a development priority right now.

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.

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.

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.

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.