Mlem for Lemmy

5524 readers

1 users here now

Official community for Mlem, a free and open-source iOS Lemmy client.

Rules

Keep it civil.
This is a forum for discussion about Mlem. We welcome a degree of general chatter, but anything not related to Mlem may be removed at moderator discretion. This is not a forum for iPhone/Android debate. Posts and comments saying nothing but "iOS bad/I use Android" will be removed as off-topic.
We welcome constructive criticism, but ask that it be both precise and polite.

FAQ

When will insert feature here be implemented?
- Check our issue board--if there isn't an issue open for the feature you want, feel free to open an issue or make post! Just remember that devs are people too--we're doing this for free in our spare time, and building a quality app takes a lot of patient work.
Is Mlem available for Android?
- No. Mlem is written using SwiftUI, which is not currently supported on Android. If such support becomes available, we will look into bringing Mlem to our Android friends.
How do I join the beta?
- We are currently testing our new 2.0 codebase on TestFlight. We have two beta groups: a weekly group that receives the current state of our development branch every week, and a stable group that receives a curated pre-release build at the end of each development cycle.
- Join the weekly beta
- Join the stable beta
How do I join the dev team?
- Head over to our recruitment channel, or go straight to our GitHub and read CONTRIBUTING.md to get started.

Download Mlem for iOS

GitHub

Website

Donate to Mlem

founded 2 years ago

MODERATORS

ericbandrews@lemmy.ml

darknavi@vlemmy.net

Kronusdark@lemmy.world

New testflight version? (lemm.ee)

submitted 2 years ago by fer0n@lemm.ee to c/mlemapp@lemmy.ml

5 comments fedilink hide all child comments

Since a bunch of new commits/features have been accumulating over the last three weeks, I was wondering if there’s a specific reason for not putting them in a new TestFlight build?

There’s also a few pinned posts that can probably be unpinned if I may add :)

you are viewing a single comment's thread
view the rest of the comments

[–] ericbandrews@lemmy.ml 13 points 2 years ago* (last edited 2 years ago) (1 children)

We're currently elbows deep a backend overhaul that should smooth out a ton of weird little state issues (things like the saved button "flickering" and interactions waiting on network round trip to apply). This touches so much of the app that shipping a TF now would turn up a ton of stale-on-arrival bugs, so we've been holding off shipping a TF until we get that merged.

By the same token, we're targeting a TF build more or less the moment that drops--the PR is https://github.com/mlemgroup/mlem/pull/556 and it just entered draft yesterday, so I'm hoping to have it in by the end of the week.

Re: pinned posts, that's an instance sync issue as far as I can tell--they're not pinned on .ml, but we've heard similar reports from beehaw users.

[–] fer0n@lemm.ee 5 points 2 years ago (1 children)

Fair enough, I‘m certainly not trying to rush anyone I hope that didn’t come across that way. I was just wondering about the reason and that seems to be a pretty good one. Thanks for taking the time to answer :)

[–] ericbandrews@lemmy.ml 3 points 2 years ago (1 children)

No worries! This has definitely been the longest span between TF builds.

By the way, I've gone and deleted all the posts that weren't unpinning properly--are they still showing up for you, or has that fixed it? There should just be the 1.0.1 announcement pinned and nothing else

[–] fer0n@lemm.ee 3 points 2 years ago

All are gone except for this one which I guess is on purpose, so looks good thanks :)