...but why would it be any different now considering it has been an ongoing issue and security threat since day 1. It is funny in light of how folks were discussing the iPhone X and upgrading to the "latest". Apparently, with Android, if you aren't buying a new phone ever 2 years (MAX!), you are leaving yourself open to all sorts of issues that come with being, essentially, abandonware.
--------------------------------------
Conclusion
We’ve seen that Android devices appear to be getting more out of date over time. This makes it difficult for developers to target “new” Android API features, where new means anything introduced in the past few years. It also means that there are a lot of Android devices out there that are behind in terms of security. This is true both in absolute terms and also relative to iOS.
Until recently, Android was directly tied to the hardware it ran on, making it very painful to keep old devices up to date because that requiring a custom Android build with phone-specific (or at least SoC-specific work). Google claims that this problem is fixed in the latest Android version (8.0, Oreo). People who remember Google’s “Android update alliance” announcement in 2011 may be a bit skeptical of the more recent announcement. In 2011, Google and U.S. carries announced that they’d keep devices up to date for 18 months, which mostly didn’t happen. However, even if the current announcement isn’t smoke and mirrors and the latest version of Android solves the update problem, we’ve seen that it takes years for Android releases to get adopted and we’ve also seen that the last few Android releases have significantly slower uptake than previous releases. Additionally, even though this is supposed to make updates easier, it looks like Android is still likely to stay behind iOS in terms of updates for a while. Google has promised that its latest phone (Pixel 2, 10/2017) will get updates for three years. That seems like a step in the right direction, but as we’ve seen from the graphs above, extending support by a year isn’t nearly enough to keep most Android devices up to date. But if you have an iPhone, the latest version of iOS (released 9/2017) works on devices back to the iPhone 5S (released 9/2013). If we look at the newest Android release (8.0, 8/2017), it looks like you’re quite lucky if you have a two year old device that will get the latest update. The oldest “Google” phone supported is the Nexus 6P (9/2015), giving it just under two years of support.
If you look back at devices that were released around when the iPhone5S, the situation looks even worse. Back then, I got a free Moto X for working at Google; the Moto X was about as close to an official Google phone as you could get at the time (this was back when Google owned Moto). The Moto X was released on 8/2013 (a month before the iPhone 5S) and the latest version of Android it supports is 5.1, which was released on 2/2015, a little more than a year and a half later. For an Android phone of its era, the Moto X was supported for an unusually long time. It’s actually a good sign that things look worse as look further back in time, but at the rate things are improving, it will be years before there’s a decently supported Android device released and then years beyond those years before that Android version is in widespread use. It’s possible that Fuchsia will fix this, but Fuchsia is also many years away from widespread use.
In a future post, we’ll look at Android response latency is also quite interesting. It’s much more variable between phones than iOS response latency is between different models of iPhone.
----------------------------------------
For Don who loves graphs and charts:
Tom