2 Billion Downloads & Other Milestones from 2024 So Far | Flathub Documentation
docs.flathub.org
It's been a busy year, and our platform and developer community-building efforts are paying off. Let's take a look at what we've been up to over the last six months, and measure its effect.

We’re back with some new milestones thanks to the continued growth of Flathub as an app store and the incredible work of both our largely volunteer team and our growing app developer community:

  • 70% of the most popular apps are verified
  • 100+ curated quality apps
  • 4 million active users
  • Over 2 billion downloads
  • LeafletEnglish
    12•27 days ago

    Edit: it they’re counting updates, then this number probably is accurate, so the bit questioning the number can probably be disregarded

    I wonder how inflated that 4 million active user number is. They say it’s measured by “count[ing] the number of updates to that runtime we’ve served between two releases”. But that method doesn’t account for people distrohopping/reinstalling or QA testing by distros.

    I maintain a snap package and something I really like about the Snap Store is the metrics they give. Note that this data is aggregated, I can’t see anything specific about a user. I am able to see:

    • weekly active users
    • distro and version
    • CPU architecture
    • country
    • which version of app
    • which channel (stable, beta, edge, etc)

    But Flathub only measures total downloads. An app could get a thousand downloads and those thousand people could immediately uninstall the app and you would have no way of knowing that. With snap, you would see a week later a drop off of a thousand users.

    • @[email protected]English
      11•28 days ago

      Measures are cool, but a bunch of people would start to complain about telemetry. And opt-in telemetry in this kind of metrics is not relevant.

    • Fonzie!
      2•28 days ago

      How does it measure weekly active users? Does it keep track of who runs the application? And how does this account for distro hoppers and QA testers?

      • LeafletEnglish
        2•27 days ago

        I’m not 100% on the details, it’s hard to find good documentation on this, but here’s my understanding.

        Every machine with snap install has an ID associated with it. Whenever snap refresh is run, a list of installed apps is sent back to Canonical so that Canonical can fetch updates. But they also use that list is also used for generating metrics. Users aren’t double counted because of the unique ID associated with the install. So Canonical just needs to keep track of all the IDs in the last week who’ve checked for updates and count them up. That final number is then shown to maintainers of the snap.

        Snap isn’t checking if you actually open the snap though. It’s just counting people who have the app installed.

        • Fonzie!
          1•27 days ago

          But they also use that list is also used for generating metrics

          But isn’t that the same as Flatpak’s “X clients download updates”-metric?

          Users aren’t double counted because of the unique ID associated with the install.

          How to they associate that with the user or the machine? Rather than the amount of snapd clients/OS’s with snapd on it? (as to not count one person with two Linuxes double, which Flatpak does)