I found a bug once in our content that only affected Firefox. Old versions of articulate whouldnt start properly. Not somthing I could fix on my own as i meeded anyoher department. I brought it to the attention of the managers. They didn’t want to fox it as apprently Google analytics showed only .4% of our user base was using Firefox. I manged to convince them its part of our user commitment to ensure that we work consistently across all browsers, but it was a pain.
That’s the main issue of using analytics and telemetry on something that’s used by power users: most of them disable/block them, so the real reported usage is much lower
Exactly. When the planes come back from battle, you put armor on all the places where the bullet holes aren’t, because that’s where the planes that didn’t make it back were shot.
I found a bug once in our content that only affected Firefox. Old versions of articulate whouldnt start properly. Not somthing I could fix on my own as i meeded anyoher department. I brought it to the attention of the managers. They didn’t want to fox it as apprently Google analytics showed only .4% of our user base was using Firefox. I manged to convince them its part of our user commitment to ensure that we work consistently across all browsers, but it was a pain.
That’s the main issue of using analytics and telemetry on something that’s used by power users: most of them disable/block them, so the real reported usage is much lower
If only being part of the .4% was like being part of “the 1%”.
Maybe it was that low because the site didn’t work properly on Firefox…
Exactly. When the planes come back from battle, you put armor on all the places where the bullet holes aren’t, because that’s where the planes that didn’t make it back were shot.