I keep seeing that there’s “reasons” for it, but never any expectations that it will ever be fixed. Is it a non-fixable issue? None of the other apps have this problem except this one.

  • fer0n@lemm.ee
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    1 year ago

    You probably have heard this before, are you using the native version? It’s somewhat better there, but still an issue.

    Voyager is built with a different framework (ionic/capacitor) than e.g. memmy (react native afaik) or Mlem (SwiftUI). The part that’s causing this isn’t done by the devs so it’s more or less out of their control. I’m pretty sure it can be fixed, I just don’t think it’s a high priority for whoever could fix it and if it’s an issue in iOS (is it a problem on Android as well?) or the framework.

    So the fix for aeharding would be to use a different framework, which I’m pretty sure is not going to happen. But there are many other apps out there, feel free to pick one that doesn’t have this issue.

    • DrM@feddit.de
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      It’s definitely also an issue on Android, but far less frequent than on iOS. On Android it’s a minor inconvenience, on iOS it’s starting to become annoying

  • kadjiis@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    2
    ·
    edit-2
    1 year ago

    If you’re on iOS try installing as a native app from the App Store instead of using the web app. The issue does not appear there.

        • fer0n@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          In the PWA it actually froze up completely while you kept swiping, in the native app it’s there for half a second after swiping back. Far less noticeable and less severe, but it’s definitely still there for me.

  • Elderos@lemmings.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    1 year ago

    I switched from voyager because scrolling gets laggier over time, up the point of beong barely usable. I liked the app otherwise, and I commend the overall UX, but the app is irredeemable until this gets fixed imo.

    • fer0n@lemm.ee
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      Are you talking about the freeze after going back where you can‘t scroll for a second? Or the scrolling itself is stuttery? For me the scrolling itself is buttery smooth which actually many of the other apps don’t manage to do. But that’s just on my device.

        • fer0n@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          That sounds annoying :/ For me, as I mentioned, it’s actually the other way around. Voyager is the most reliable while many of the others are plagued by stutters.

        • aeharding@lemmy.worldM
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Are you using the PWA or the version from the App Store?

          I’ve experienced stuttering with the PWA but no the app store version for some reason.

          • Elderos@lemmings.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            It was the PWA version. That is good to know, I moved to Sync since due to this issue, so far so good!

    • PrataiOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      Same. It’s too bad too. Not a bad app.

  • Makeshift@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    is this the issue where the page keeps jumping around when you scroll? I keep losing my place while browsing because it jumps 2 posts down or up from where I was

    • ribboo@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      No this issue was actually fixed in the last release. At least for the AppStore version.