• Fake4000@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    9 months ago

    Thank you @[email protected] for the update.

    I noticed one thing, scrolling has been improved drastically and it has become very smooth.

    What was updated that made it buttery smooth?

    • MV [Jerboa dev]@lemmy.one
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      9 months ago

      The biggest performance changes should be from 0.0.56

      Due to a compound of factors:

      Those factors lead to that we do a lot less recompositions now. Which means that that each frame we do less calculations, “keep the same UI element as before”, it is smarter at about detecting elements that stayed the same and should not be recalculated. So each frame is cheaper and it can do thus more per second

      In 0.0.60 I have updated the baseline profiles (It ships the app with AOT bindings, instead of which you would get after a week from release on the playstore)

      Google does some amazing work, it just takes them a long time. Once this patch lands we should see more optimizations https://issuetracker.google.com/issues/241154852

      I also recommend list/small card view, if you prefer the feed to not jump due to images loading in. At some point i’ll refactor some infra so that I can Image and post preload feature out. So that it should be able to instantly load those images. But that is quite deep in the backlog.

      • Fake4000@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        9 months ago

        Absolutely appreciate all these details. Thank you so much for the detailed reply. Love it.

      • Fake4000@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 months ago

        Would you know what happened that made it smooth?

        It was a complaint I had about jerboa.

        • THE MASTERMIND@lemmy.today
          link
          fedilink
          arrow-up
          2
          ·
          9 months ago

          No but my guess is they fixed some bugs that caused it to ? Or fixed the issue seperately ? Anyways i don’t think it is addressed in github release notes