They seem to be too big for what devs claim to be a ‘minor patch’ and yet too small to suggest a complete reinstallation of the app. Is there some technical reason behind it? I would like to request an ELI5 for this.

    • ono@lemmy.ca
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      App stores and their systems don’t usually have the ability to deploy diffs

      Google Play has had this ability for over a decade. They call it smart updates, though the general idea is often called delta updates. Apple has the ability, too, though I don’t know when they started.

  • dallen@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    This will completely depend on how and what is being distributed.

    For example, I used to work on an app where assets (3D models, images, etc) were appropriately diff’d during updates but the binaries were not.

  • lightsecond@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    The Google Play Store uses a technique called delta patching to calculate the diff server side and avoid transferring parts of the app that haven’t changed since your original installation.

    This is understandably not perfect because they want to avoid load on their servers and also the extra processing on your device to “unpack” it. So what you have is a happy medium between sending the entire app again and sending strictly the diff.