So, I should preface this with a few big caveats!
- I am not a metrics guy, nor do I pretend to be.
- This post will not give you absolute numbers of users.
- This post is not meant to show any sense of penetration into the market
- Ignores all things Firefox OS for the purposes herein.
- I present this as an attempt at data only and no pre-judging of where we should go, nor what we should do.
- I am explicitly trying to avoid color commentary here, and allowing the reader to draw their own conclusions based on the static data.¹
What this series will attempt to show is:
- Where the current marketshare is on Android OS’s (with citations where possible)
- Where our (Firefox for Android) userbase is
- Where we invest in builds/tests (due to length, this will be in a Part 2 — Will link from here once published)
- How what we do in Release Engineering correlates to our known market (based on these stats). (also in Part 2)
Now to the juicy bits!
Google’s own stats on Android Marketshare
Currently Android has a pretty healthy marketshare on the later OS’s, and the earlier ones are seeing very very diminishing returns.
Android Usage Share on Dec 3, 2013, from http://developer.android.com/about/dashboards/index.html
This data was all from http://developer.android.com/about/dashboards/index.html so feel free to see updated data as of whenever you are reading this.
Stats from Google Play for “Firefox for Android”
Before we begin with the data, I need to clarify something readers may not be aware of at first glance, “What is an Install”
Install in this context is any currently active device which has Firefox installed on it. It does not actually indicate frequent use.
Installs by OS – Release (org.mozilla.firefox)
Yes, you see that right, this is 81.4% of our GA users on some version of Android 4.0+.
Installs by OS – Beta (org.mozilla.firefox_beta)
Our beta audience is pretty similar with 83.59% on an Android 4.x or higher.
Installs by Chipset
Selecting by Chipset is a bit harder, since to do so we have to take a factor of how Releng does our Play Store releases (different buildID’s to factor to different chipsets). I am doing this by a feature of the play store, namely “Export as CSV” which gives buildID info
So with that in mind, here is the data:
The caveats to note is that I only gathered data from today’s Google Play installs, and I aggregated all installs over all versions, even ones that are multiple years old. We also do not have x86 released officially yet, so we only have beta users using that version.
Coming in Part 2:
- Where does Mozilla Invest build and test resources for Android?
- How does this compare to Mozilla’s Testing Infrastructure?
¹ - This post as-is is indeed intended to be data without analysis/commentary. I don’t feel I’m greatly suited for the latter compared to other people possibly reading. In Part 2 I intend to show some correlaries-as-data to what we are doing inside Release Engineering as it compares to our users at large. I’m currently hoping to also write it devoid of any assertions/commentary.
- The underlying reasoning here is to help spur thoughts and commentary in others in order to further our mission using data, while at the same time without inserting my own opinions or biases into what I am presenting with this 2-part series. I do not yet know if I will do a commentary piece referencing these posts or not, and I may do so, I just don’t yet plan to.