(NOTE: Originally published at https://www.linkedin.com/pulse/chrome-updates-traction-kevin-kostrzewa/)
Analytics are fun.
My current obsession is determining how long it takes for a new major version of Google's Chrome browser to receive "traction" in the marketplace after it's been released.
Chrome's automatic update feature was an inspiration to my patent, so I could design desktop software that had multiple independent products, separately versioned, that allowed automatic updating of those products, even while being run in an enterprise.
When Chrome has a new major update, imagine millions of users randomly getting notifications to "please restart to realize the update".
What I wanted to know was how long from the first download of the new release to when the downloads had "traction" in the marketplace and usage had consistently overtaken the prior version.
Using some proprietary analytics that I can't share here, my back of the envelope calculations put that at 8 days. Admittedly, that's just for a single release that I tracked. I'll check that against future releases as well.
My next analytics flex will be on when the previous Chrome release is dead (or near dead) so the new version has dominance in the marketplace.
Both of these pieces of data are essential to determining when new front end development features (html, javascript) can and should be utilized in a piece of web software.
As an aside, I'm sure all of this data is publicly available by Google. I'm deliberately not looking it up yet because I want to solve the problem to make sure my tools and data set are in line with reality.
Analytics are fun.
My current obsession is determining how long it takes for a new major version of Google's Chrome browser to receive "traction" in the marketplace after it's been released.
Chrome's automatic update feature was an inspiration to my patent, so I could design desktop software that had multiple independent products, separately versioned, that allowed automatic updating of those products, even while being run in an enterprise.
When Chrome has a new major update, imagine millions of users randomly getting notifications to "please restart to realize the update".
What I wanted to know was how long from the first download of the new release to when the downloads had "traction" in the marketplace and usage had consistently overtaken the prior version.
Using some proprietary analytics that I can't share here, my back of the envelope calculations put that at 8 days. Admittedly, that's just for a single release that I tracked. I'll check that against future releases as well.
My next analytics flex will be on when the previous Chrome release is dead (or near dead) so the new version has dominance in the marketplace.
Both of these pieces of data are essential to determining when new front end development features (html, javascript) can and should be utilized in a piece of web software.
As an aside, I'm sure all of this data is publicly available by Google. I'm deliberately not looking it up yet because I want to solve the problem to make sure my tools and data set are in line with reality.
No comments:
Post a Comment