We’ve been hard at work over the past couple weeks on our 1.1 build. We’re excited to be rolling out our first set of new features to the TestFlight beta (and, soon, to the App Store). The highlights:

  • Editing posts and comments
  • Account quick-switching. You can access the new accounts menu by long pressing on the profile tab, swiping up from the tab bar, or going to your profile and using the button in the navigation header.
  • More post customization
  • Compact comments option. Also, the interaction bar now properly collapses when you collapse a comment.
  • Organized the settings and gave them a facelift while we were at it
  • Unread count on the inbox tab (this can be disabled it in settings)
  • The inbox menu now has options to show only unread and mark all messages as read

We’ve also got a ton of bugfixes, backend changes, minor tweaks, and other goodies for you. You can see the full details on our GitHub page, or just jump into the app and see what’s new. Check it out and let us know what you think!

Cheers,

The Mlem Group

Download Mlem on the App Store

  • Eric@lemmy.mlOPM
    link
    fedilink
    English
    arrow-up
    30
    ·
    1 year ago

    Some of the features that are coming in the next week or two:

    • Fully-fledged media viewer for gifs and images
    • Marking and hiding read posts
    • Guest mode
    • Crossposting
    • Image upload
    • bagfatnick@kulupu.duckdns.org
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      1 year ago

      Thanks for all the hard work. I’m particularly enjoying the compact comments. I just realised there’s quicklook for images in comments, which is really handy. Is that likely the same implementation for the upcoming media viewer?

      EDIT: on messing about further, it’s the same interface for post pictures as well. I like it!

    • Eric@lemmy.mlOPM
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      That’s a bug–we didn’t remove it, though we did turn it down a little and change how we manage haptics at the backend. It looks like that solution might be a bit dodgy–we should have it much more robust in the next build or two