ericbandrews

Should be pretty straightforward, we'll look into it for 2.0

TL;DR: Mlem v1 is not fast; Mlem 2.0 (announcements coming soon!) will be.

We’re aware of a number of performance issues with the current codebase, which all together result in the app not behaving as responsively as we’d like. Unfortunately these are largely due to design choices made during the hectic sprint to App Store release last summer, and so are infeasible to fix without rewriting the app from the ground up—which is why that’s precisely what we’re doing. Our 2.0 build should be significantly faster; we’ll have some announcements about that in the near future.

Sure! One of the big things we’re reworking for 2.0 is how we handle accounts, which includes changing the format of how we persist account information. The compatibility changes in this build add extra decoding logic to the account persistence system so that both v1 and v2 can load a saved account regardless of which version saved it.

Thanks for the bug report, we're looking into it!

This is not possible in the current version, but our 2.0 rewrite gives us the level of granular color control required to effectively implement such a feature, so we'll be sure to include it when that ships.

This is a known issue, and one that has us completely stumped--we don't have a single line of code that touches anything related to audio. We're monitoring it closely as we bring our 2.0 codebase online to try to figure out what's causing it, and aim to have it fixed in 2.0.

Gif support is still one of our major outstanding tasks. We are currently working on a 2.0 version of the app, and are hoping to ship it with full inline gif support.

Thanks for the feedback! We're aware that the iPad version isn't up to the standards of the iPhone app--we're a very small team, and so lean hard on Swift's automatic multi-platform features to make the iPad app even feasible within our development bandwidth. We're looking into ways we can improve the iPad experience without introducing unsustainable technical overhead as part of our ongoing 2.0 overhaul, and we'll be sure to take your suggestions into consideration.

This behavior can be customized under Settings -> Links -> Tappable Links. By default it uses "contextual," which will display the full link in large contexts and just the title in compact contexts (e.g., comments if you have comment display set to "compact"). Setting it to "large" will always display the full link regardless of context.

It is our policy not to make features-for-donations transactions, as we feel that would compromise the spirit of the project and set a dangerous precedent that could lead to development becoming beholden to the wealthiest donors. We really appreciate your enthusiasm and your generosity, though--we're going to be busy for a little while getting 2.0 up and running, but we can tentatively scope widgets for 2.1!

It's currently live on the TestFlight beta! We're planning to roll it out to the App Store in the next few days.