The monthly Android version battle - Dec '14 and Jan '15

Introduction

In December there was nothing exciting to announce. Android 5.0 was enrolled on some Android devices but not enough to gain 0,1% market share, and the same counts for January. Meaning the current Android versions continue the same way as they did before. But let's see what that means in terms of real numbers.

Show me the numbers

Android 4.1 and 4.2 switched places in the market share list. Android 4.4 is on a stable level for the past 7-8 months. This is first version that stays this stable over a long period of time. My explanation for this is the steady sell in phones and when the phones where replaced with Android 4.4 the cheap tablet segment is now selling tablets with Android 4.2. So the phones might have decreased but the overal number stays about the same because of the tablets. Android 4.4 is still growing steadily and I already dare to claim that my previous predictions (that this version will get to at least 50-60% market share) is within reach. Mainly because also the cheap Android phones that are sold now run Android 4.4 and the tablets will follow soon as well as smart watches that become more popular. Android 5.0 still does not have enough market share to be shown in the figure, but I'm sure more phones will get the 5.0 update and also some phones will be sold with Android 5.0 so at least 0,1% next month will most likely happen. Another thing is that next month KitKat will be bigger than Jelly Bean if the increase/decrease flow will remain as is. There might also be a switch in places in the lower % segment (Android 2.3, 4.0 and 4.3). Android 2.3 and 4.0 are now really almost depreciated. From my point of view, all old versions with less than 5% market share are depreciated, they have no future, as a developer you should put more time in newer versions.

Android versions in order of current market share

  1. (-) Android 4.4 with 39,1%
  2. (+1) Android 4.2 with 20,3%
  3. (-1) Android 4.1 with 19,2%
  4. (-) Android 2.3 with 7,8%
  5. (-) Android 4.0 with 6,7%
  6. (-) Android 4.3 with 6,5%
  7. (-) Android 2.2 with 0,4%
 

Android code names in order of current market share

  1. (-) Jelly Bean with 46%
  2. (-) KitKat with 39,1%
  3. (-) Gingerbread with 7,8%
  4. (-) Ice Cream Sandwich with 6,7%
  5. (-) Others combines with 0,4%
 

Estimates for February 2015

  1. Android 2.3 (Gingerbread), will keep on decreasing (-1,5%)
  2. Android 4.0 (Ice Cream Sandwich), will keep on decreasing (-1%)
  3. Android 4.1 (Jelly Bean), will keep in decreasing (-2%)
  4. Android 4.2 (Jelly Bean), will remain stable, might decrease a bit (-0,1%)
  5. Android 4.3 (Jelly Bean), will decrease (-0,5%)
  6. Android 4.4 (KitKat), will keep in increasing (+5%)
  7. Android 5.0 (Lollipop), will finally show signs of life (+0,1%)

Sources:

  • https://developer.android.com/about/dashboards/index.html


Comments

Post a Comment

Popular posts from this blog

PowerShell - How to overcome Azure VM's fixed resolution limitation

Image
Intro This is the first in a series of PowerShell blogposts. I don't know a lot of PowerShell so I'm going to cover this part very short. What is PowerShell? PowerShell is a very powerful framework you can use to automate tasks. For more info, use Google or check the Wiki:  https://en.wikipedia.org/wiki/PowerShell For my current project we use Azure VM's that we use as selenium-grid (hub and nodes). And Visual Studio Online for kicking off builds. So I started to use a fair share of PowerShell in my test automation process. During the setup I came accross a couple of problems that I want to share with you all which I'll spread across a couple of posts. And we start with Azure VM's that have a fixed resolution of 1024 x 768 and how to overcome this issue/limitation. Azure VM's resolution limitation  Let's start with the problem we faced. Our website under test, requires the test machine to have at least a certain resolution ( Which is > 1024
Read more

TA Basics: Website Test Automation on mobile devices via Appium server

Image
Recently I have been focussing on test automation with mobile devices. Specifically Android and iOS (no Windows phone because that platform is as good as dead at the moment). I first wanted to make a complete manual from setting up software and devices/simulators up to a small test script. But due to lack of time I'll focus on specific parts. If you have any questions reguarding the setup, feel free to contact me. So all that said, let's get to the point. The internet is full of blogposts, video's and examples of people testing mobile apps. However I don't test an app, I want to do some web test automation on mobile devices. It took me quiet some time to figure out what exactly I had to use to get it all to work as needed for my project. Setup Mac mini running OSX 10.13.4 High Sierra (Mac machine is needed for iOS simulation) Ruby version 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17] Appium desktop version 1.4.1 (with Appium server 1.7.2) lapis_laz
Read more

TA: Who doesn't like proxies? Me!

Image
Are you on a company network that is using a proxy to connect to the internet? And do you want (or are you planning) to connect your tests to an external selenium-grid. Than stay tuned, before you get lost in a bunch of answers on the internet that don't resolve the issue you're facing. Source:  https://nl.wikipedia.org/wiki/Proxyserver I'm on a new project and looking into Robotframework. But then I bumped into an issue with the POC I had to make which might result in me convincing the company to switch to Ruby. Anyway long story short. They use a proxy and although the internet has all the answers, you do need to know what specific question to ask to get the correct result. And since proxies are not used that much anymore, it's hard to find the skilled people to help you out and push you in the right direction for a solution. The setup To access the internet, I need a configuration on my computer that will tell Windows to connect to a proxy server. I
Read more