Download the TestFlight beta for iOS 16+
After a massive reorganization and recruiting almost 20 new developers and designers from the community, we’ve made a HUGE amount of additions and improvements to the app, with many more to come! Yay!
NEW ADDITIONS
- Redesigned interface! NEW POSTS, COMPACTS POSTS, ALL THE THINGS!
- Updated Settings Tab
- Tap to collapse comments/threads
- Long post text is now truncated so they don’t take up your whole screen. They will have a maximum height.
- Increased contrast between post/comment cards and background
- The way the application interacts with the Lemmy API has been improved, this should reduce crashes in multiple places
BUG FIXES
- Tapping community links will no longer crash the app, instead an alert shows saying they’re not currently supported (we’re working on it now, it needs a few different chunks of work completed)
- Duplicate/looping posts when scrolling feeds should no longer happen 🤞
- Rapid scrolling through feed should no longer cause crashing 🤞
- Mlem icon is now brighter!
KNOWN ISSUES
- Some images may extend beyond the post card bounds in Card View
- In compact mode, link previews may not load
- Comments still have old up/downvote buttons
MORE TO COME
- Full a11y compliance which should work perfectly with iOS’s Accessibility functionality like Guided Access and Screen Reader. (Thanks to contributor Weston for your expertise and audit!) Note: we weren’t able to work this into the current build because of the constant changes to the interface, but some/most of it should be in the next build!
- New Profile Tab and Messages Tab
- New & improved fullscreen image viewer (not ready in time for this release)
- Inbox notifications (not Push, as that takes more work-- more on that later)
- Colored thread indicators
- Swipe-to-vote
- Post/comment saving
- Updated NSFW tag/blur
Again, please keep in mind that this is an early beta. As such, it’s not feature-complete and there will be bugs and unexpected behavior. Enjoy testing, and we look forward to hearing your bug reports via TestFlight and your feedback! You can comment here or come chat with us in The Mlem Space on Matrix.
PS, and because lots of people have asked-- Mlem app will never support iOS 15. Sorry, but we’d have to rewrite the app from scratch, and that’s not something we’re gonna do. Additionally, kbin support isn, for now, out-of-reach due to incompatibilities between the kbin and lemmy APIs. Although this may change in the future, for now, it’s not going to happen.
Cheers!
The Mlem Dev Team
Please remember everyone that Apple still treats TestFlight builds like AppStore releases, it has to go into review first once it’s accepted you’ll be able to see the update :)
Yes and no. In this case, the delay is because we updated the version number (0.0.6 —> 0.0.7) instead of simply the build number (which we also bumped to 23). This is what triggered the review. Hopefully it will be a short process!
Has it been updated in TestFlight yet? Still shows version 0.06 for me :(
It’s currently in review by Apple. It should come out soon though!
This. Sorry for the unexpected delay!
For me as well - if I click the TestFlight link in the post it tells me the Beta test is full. :( Can’t wait to check out the new version!!
Give it some time. It’s possible they uploaded it to TestFlight when they made this post and it takes Apple’s servers a bit to actually publish it.
I’m only showing .0.0.6 (22) in Testflight. So maybe it’s awaiting approval still.
Same here, it’s set to auto update too, so not sure what might be going on
Make that 3, tried uninstalling and reinstalling via test flight but having the same issue.
Same here
It is available for me now.
Just checked back and it’s available yes. It looks great as well! Thanks Mlem team :)
20 new developers! Damn. Thanks for the hard work, everyone.
It’s somewhat exciting to be a part of this journey so early on; Lemmy will obviously continue to change as it adapts to an influx of users, so I’m sure you guys have your hands full. Looking forward to the continued progress of the application.
To be specific, that’s 20 new contributors. 7 or 8 are graphic and UX designers, and the rest are devs.
This is awesome, thanks everyone for your work!
Removed by mod
New feed with standard height posts looks much better and scrolling seems smoother 👍
Is long press to share on posts new in this release? I don’t remember that in prior releases.
Glad to hear it!
And yep, that’s a new feature.
Aw the beta is full :(
Sorry, kids! We’ve hit our 10k limit!
Upvote for popularity, downvote because I’m not in the 10k :D
sorry (not sorry) that our test group maxed out so fast!
I’m also seeing the beta as full, boo
https://lemmy.ml/c/memmy is still available for testing for iOS. I like both!
Really liking the new design and it fixed my main UX issue by condensing long posts. Great work.
That was probably my biggest gripe. Not enough to not browse on mlem, just a small annoyance and glad it’s been addressed.
It was bad when one of the Trump indictment post was constantly at the top of my posts and was like 14 pages long.
Really nice update.
I hope in the future we can choose have thumbnails on the right so we can click them easier and the left side text can all begin at the same point, cleanly aligned. And self posts etc won’t need a thumbnail, which will cut down on the busy and rigid look.
Something somewhat like this:
Thanks!
In the future we plan to offer many more customization options, including which sorts of posts get thumbnails and which side thumbnails show on. It’s not in active development right now (we’ve got some core features like NSFW blurring that have higher priority), but I built the post display with customizability in mind so you have my guarantee that it’s coming.
Very nice update, well done! Thanks for your work!
Not sure if it’s been reported but posts are repeating multiple times. Not sure if this would be the api bugging out or the app?
this issue is being tracked. we’re not sure what’s causing it yet. thanks!
Unfortunately I just get “Something went wrong” since updating to 0.0.7
yeah, some lemmy instances are slammed and throwing SSL authentication errors, and this is the response. we’re already working on creating more robust error handling and changing the UX for those errors. it’s very annoying, but we can’t control the lemmy instances and whether they’re up or down. what we can control is how the app reacts when it experiences an error, so we’re working on making it less annoying!
Yeah I’m not even seeing replies (on the web version) from other instances any more. It’s weird because just browsing communities (on web) still works fine for me.
Unfortunately Mlem hasn’t worked once for me since the update, but perhaps it’s just a coincidence that it happened at the same time.
Do I have to make accounts on multiple instances for things to work or should I just wait for scalability improvements?
Looks seriously great. Lots of improvement. The crashing stopped and has been replaced by errors. Presumably issues with the server rather than the app.
The compact view looks slick. It would be better if clicking the thumbnail brought you directly to the image such as in apollo.
I’d also love swipe gesture for voting.
The ‘new post’ constantly having the url for your other brew app is pretty unwelcome. Especially in its current form where it looks like a hyperlink. If it was gray and user-typed URL text was white, it would be much more acceptable.
This app looks slick! Unfortunately I was too late to join the TestFlight beta. Is there a rough ballpark estimate when we might see this app on the App Store? Keep up the good work :)
we’re aiming for July 1 for 1.0 🤞
I’ve just updated from 0.0.6 to 0.0.7, but found it wouldn’t show posts. I kept seeing “Something went wrong. Sorry, something unexpected happened. Please try again.”
I signed out and in again, and now I see “Mlem couldn’t fetch you account’s information. File a bug report.”
I see an existing issue https://github.com/buresdv/Mlem/issues/181 which might be related. Should I create a new issue, or describe what I’m seeing as a comment on that issue?
honestly, it could be this, or it could be load timeouts from overloaded instances. it’s difficult to tell the difference from our end because the LemmyAPI isn’t very good at telling us what caused an error, so we have to triangulate it ourselves. whichever it is, we’re looking into it, so no need to file an additional report. thanks, though.
