Android Jelly Bean Hits Sweet Sixteen as Android 4.x Installs Rise

According to newly updated statistics, Android Jelly Bean now accounts for 16% of all of the devices shipping with Google’s mobile operating system.

These statistics, brought to us courtesy of the Android Developer Dashboard, show the adoption rates of the latest two updates to Android, Android 4.1 and 4.2, are gaining steam. Their combined 16% breaks down in favor of Android 4.1 which launched in June 2012 at 14.9% , and Android 4.2 which launched in October 2012 and accounts for 1.6%. These statistics are compiled by taking a snapshot of all the Android devices that access the Google Play Store over the course of a two week period.

android-jelly-bean-575x442

These numbers imply that not only are the latest and greatest Android devices picking up steam on wireless carriers, more users may be easily getting updates from their wireless carriers who typically try to steer clear of issuing non-essential fixes for older devices like full operating system upgrades.

Android Jelly Bean’s rise to third largest operating system in the Android ecosystem comes good news for Google as complaints of “fragmentation” and handsets not being upgradable to newer operating systems continue to be leveled at Android, which is now the world’s largest smartphone operating system. However, these statistics won’t satisfy most of those critics, as even today Android 2.3, which launched back in December 2010, continues to dominate the Android ecosystem overall at 44%.

Getting the latest version of an operating on as many user’s smartphones is crucial for any operating system. Application stores have increasingly become the center of smartphone operating system’s advantage.

As newer versions of Android are introduced, advances in the way developers create applications are sometimes not compatible with older versions of Android and usually result in developers choosing to only focus their efforts on the newer, easier to program versions instead of maintaining backwards compatibility with older versions that may need workarounds or additional code to work correctly.

  

Leave a Reply