Note - The data behind these graphs (created using Redash) automatically updates every 10 minutes.
These Monthly Download stats begin in August 2018, when we moved our primary download location from GitHub to our own infrastructure.
GitHub does make download stats available through their API, and it would be useful to add the historical (and ongoing) downloads from GitHub to this too.
There’s about 1/2 million downloads of our 3.12.2 release from GitHub (as of 2023-04-28), that’s not counted in the graph above.
The missing chunk of download numbers (green) around the start of 2021, was when the download servers weren’t saving the download info in the backend database properly. 🤦
The 3.12 series release (green for initial release, blue for our current stable release) shows the monthly downloads are mostly in the 140k to 180k range.
The next major release (expected in mid 2023) will most likely show a download spike as people upgrade, then probably return to about the same monthly download range.
Monthly active users - non version specific count
This “Monthly Active Users” graph just shows a simple count of how many unique IP addresses (per month) are checking whether a newer version of DB Browser for SQLite is available.
We don’t have data prior to our 3.11.0 release, as we used to primarily have our downloads on GitHub which doesn’t share much information. As we serve our own downloads now, this information is available.
The numbers mostly start in October 2018, with our first Alpha release for 3.11.0.
With the first release in the 3.11 series in Feb 2019, we start to see meaningful numbers.
Monthly active users - version specific count
This graph shows similar information to the one above, but this time includes the version number.
The total number of “active users” in any given month can be slightly higher here than the graph above it, as this one includes an entry for each version of DB Browser for SQLite launched.
For example, when someone launches an older version of DB Browser for SQLite it will count them for that version, and then count them again if they upgrade to a newer version.
So, there is some potential for double counting of a user in this one.