this post was submitted on 30 Jun 2023
324 points (99.7% liked)

Memes

45172 readers
1713 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] iso@lemmy.com.tr 9 points 1 year ago (1 children)

It's good but laggy. Swiping doesn't feels native unfortunately.

[–] cowleggies@reddthat.com 6 points 1 year ago (3 children)

Are you using it as an installed PWA? I’m not having any issues with animations or scrolling. I have run into a few weird UI bugs with slide up menus within communities, but that’s about it.

[–] gkd@lemmy.ml 13 points 1 year ago (2 children)

As the Memmy dev I can also highly recommend wefwef. Great product for such a short lifespan.

[–] adude007@lemmy.ml 2 points 1 year ago
[–] fiah@discuss.tchncs.de 2 points 1 year ago (1 children)

Quick question: I noticed the API calls aren't (weren't?) compressed, is that on purpose?

[–] gkd@lemmy.ml 2 points 1 year ago (1 children)

Going outbound or inbound? Outbound the requests are super basic, inbound they are pretty large. There’s a lot of limitations on that.

For example to get basic user info you have to receive a bunch of other information that you’re not going to bother using. Hopefully in time this will get changed, because there’s no reason to be receiving so much data whenever you really only need a few bytes.

[–] fiah@discuss.tchncs.de 1 points 1 year ago* (last edited 1 year ago) (1 children)

the json coming back from requests like showing a thread was not compressed when I checked yesterday (firefox on ubuntu): https://discuss.tchncs.de/pictrs/image/1a99e758-deaa-46f6-8eff-3aa2158858ad.png

but I just checked again and now it's correctly responding with compression (chrome on windows)

[–] gkd@lemmy.ml 3 points 1 year ago (2 children)

Ohh you’re referring to wefwef. I’m not the wefwef dev, I’m the memmy dev. Thought you were talking about API calls memmy makes.

[–] fiah@discuss.tchncs.de 1 points 1 year ago

oh shit sorry, apparently I can't read worth a damn

[–] EmpathicVagrant@lemmy.world 1 points 1 year ago (4 children)

The fact that you’re not just actively engaging here, but advocating another route, makes me want memmy on apple.

[–] leftbones@lemmy.ml 1 points 1 year ago

Memmy is on Apple, in fact I think it’s only on Apple?

[–] MrCaturdayNight@lemmy.world 1 points 1 year ago

Memmy is on apple. Want no longer.

[–] gkd@lemmy.ml 1 points 1 year ago

The key to making Lemmy work in my opinion is being a real community. That means having everyone help out in any way they can and working together. Memmy alone can never fill all the gaps, nor can anything else. A wide selection of options is key to getting more people on board.

Already we are seeing varying designs and implementations, and that is great since users definitely don’t want to be locked in to a single option. Glad to see it.

[–] EliasChao@lemmy.one 1 points 1 year ago

I do have installed as a PWA, and although I’m really liking it visually, it’s a bit buggy. I’d like to know if the bugginess is because of its beta status or the fact that it’s not native.

If it’s the latter, it’d be unfortunate since it’s making my switch to Lemmy so much smoother as I feel like I’m using Apollo, which I’m very used to.

[–] iso@lemmy.com.tr 0 points 1 year ago (1 children)

IDK maybe I am being paranoid here :) Mlem feels smoother for me. It may be about frame rate too. I'm using 14 Pro and it has 120hz as I know.

[–] cowleggies@reddthat.com 1 points 1 year ago

Yeah I can also see that animations aren't as smooth as Mlem or other native apps, but it's not bad enough that it bothers me. On an 14 Pro also.

I imagine this has to do with the fact that PWAs likely don't have access to full hardware acceleration for graphics, but I also don't know enough about PWAs and iOS to know for sure.