It also doesn't help that the interaction bar doesn't collapse with the comments lmao
Re: design: as I mentioned above, compact comments are coming (and are probably going to be the default); the interaction bar is really nice from an accessibility standpoint because it doesn't hide the core interactions in swipes or menus, but does consume a lot of vertical space. We always shipped it with the intention of adding a slimmer comment mode, which we are about to merge and should be hitting the public beta soon. More generally, we were iterating our design aggressively to find a layout that is going to serve us well when we implement our big customization update (planned for 1.2, late August/early September). Some of the choices we've made should make some more sense then, and for the time being we're pretty happy with where the design has landed and don't foresee it changing much going forward (though it will be getting much more configurable).
Your feedback--positive or negative--is, as always, greatly appreciated. Thanks for helping to improve our app!
Thanks for giving us a try! We're constantly improving, and your feedback is invaluable--we're working on adding confirmations to more destructive actions for the next build.
For credentials, we don't use oauth because Lemmy doesn't support it--there's an issue open on their GitHub that should resolve that, but until then it's passwords or bust.
Good news--we decided that "some support is better than none," and quietly released the iPad app to the App Store as well. It's not perfect--we're pretty heavily leaning on SwiftUI's automagic cross-platform--and while we finish filling out our core features it's not going to get much dev time, but come 1.2 we'll make it all nice and shiny
Thanks for the download, and I hope you enjoy it! We’re firm believers in the native Swift experience, even though it takes a little longer to develop in
Mlem dev here—couldn’t agree more about Gavin, he’s a fantastic guy. Gave us some helpful tips about getting through App Store review. Massive props to him for getting that app up and running so fast.
Haha yeah we're definitely the "slow and steady" team on this one. Memmy is done in react-native, which, as the app very effectively demonstrates, is a fantastic framework for getting a smooth app out to market fast. We're using SwiftUI, which has the advantage of being the native iOS framework--it's more powerful and integrates better with the platform, but at the cost of being slower to develop in.
The image viewer is our #1 priority right now. To zoom you can tap the image once in the post view--we're working on getting a hotfix out shortly to make that work the intuitive way, where tapping the image in feed opens the quick viewer.
Longer-term, we're working on a much more robust, fully-featured media viewer, but it's a complex piece of code and we want to get it right--it's slated for our next milestone (1.1, targeted Aug 5).
There are a couple smaller reasons, but the big one is that we use NavigationStack to handle our core view navigation--it's a truly monumental improvement over the old NavigationView, and lets us do things like build an iPad version without rewriting all our nav stuff, but it is unfortunately only compatible with iOS 16+.
I know that's probably not a super satisfactory answer, but I'd rather be transparent than spin some PR nonsense at you.
We've got a much better, fully-featured, smooth image viewer in the works--the current one is a quick-and-dirty solution to people not being able to zoom in on pictures. We hope to have it out soon, but it's a complicated piece of code and we want to get it right.
Thanks for the feedback! Would you mind sharing a couple details to help us figure out what might be causing this?