Mobiles are now handy tools to connect us with the rest of the world so everyone strives for mobile apps. There are billions of apps exist in various mobile marketplaces for various purposes. Storing or bearing capacities of mobile devices are limited compared to their big sister devices so mobile users are always choosy and under stress to select only highly useful and used mobile apps.

android developer

Well if you are mobile user, do you have time to surf the Internet for your app needs, perhaps no, in many instances. Thus, what you will do? You will go to respective marketplaces like Apple store, Google Play, Microsoft Store, etc. based on the mobile OS in your devices and will run a short search to get what you want. What will you encounter there? Rating first, reviews second, and some product description at last.
 
Who is Real Culprit?
Oh! There are a lot of confusions if reviews and rating are in negative tones. Still your fast friend is recommending it by saying that she/he is using it with good user experiences. Now, let me help you to solve this mystery and your dilemma for selection. Ask your friend that which mobile OS version she is using, and ask the same question to the reviewers who have put negative reviews or rating.

I hope you will have nearly perfect answer of this query and you will find that your friend has the latest version of OS and reviewers have lower versions. In short, version compatibility is real culprit behind these negative reviews and rating. Now, question is that who is responsible, users or developers. If we believe that customer always is king, hence we can’t blame our users at all so it becomes the duty of developers to test exhaustively for version compatibility before uploading mobile app in app store.

Fragmentation on Android
The most unfortunate mobile OS platform is Android because it is an opensource so allow anyone to use any device and any version suits her/him. At other hand, this freedom is a big advantage for users with diverse needs and budget. Therefore, resulting fragmentation on Android platform becomes headache for Android developers and Android development companies.
 
Nature of Issues of Android Fragmentation
If you are an Android developer and wish to secure app market success, it is mandatory for you to beat these fragmentation issues upfront during Android development process before any cry heard from the market at postproduction phase. If you thoroughly examine the nature of fragmentation and know its causes, naturally you will able to beat them easily and in cost-effective ways.

It is true that Android platform enjoys variations in shapes of devices, their prices, form factors, OEM, hardware component and support, etc. Thus, it offers freedom of selection and usage without any vendor lock, exhortations, exploitations, and victimization by proprietary platform like things. These are the true reasons behind the popularity and growth of Android platform within the shortest span.

Versions in Android App Development
At developer point of views, Android is release new version in incremental fashion and increasing its numbers of API level gradually to meet the contemporary needs of users as well as developers to integrate various 3rd party software and services. Therefore, if we look at codename of versions along with numbers of API level and compare it with their distribution percentages we can easily take good decisions over testing and other QA issues.

For instance,
Froyo (8 API) has 0.7% distribution
Gingerbread (10) 13.5%
Ice Cream Sandwich (15) 11.4%
Jelly Bean -1 (16) 27.8%
Jelly Bean -2 (17) 19.7%
Jelly Bean -3 (18) 9.0%
KitKat (19) 17.9%

Version Overview
No doubt, the oldest versions of Android OS like Cupcake and Doughnut are extinct species in Android ecosystem and Froyo and Gingerbread are following them. Therefore, spending money on Gingerbread and older version supporting devices seems waste unless your client specifies or her targeted audience pushes you to do so. Thus, you can begin your testing from ICS and spend more on Jelly Bean version as well as extend your efforts for the latest releases like KitKat and Android L may prove highly beneficial for you and your clients.
 
Spending on Devices
It is costly affair if you are going to spending heavily on devices. Therefore, track your target audience thoroughly and define their geography as well as device and OS preferences using the latest surveying methods. If we see Android OS version above 2.3.3 are still relevant for many category of apps and usually users of ICS are capable to use the latest features and functionality of the most apps.

If your target audience coverage target permits, you to capture 60% audience begin testing from Jelly Bean versions and cover devices only from prestigious hardware vendors. Here is a comprehensive list of devices that you can spend money on and avail in your lab or prefer for remote testing using paid testing services.

For lower versions:
Amazon Kindle Fire D01400 ( 2.3.4)
HTC Desire HD A9191 ( 2.3.5)
Huawei Fusion 2 U8665 (2.3.6)
Sony Xperia U ST25i (2.3.7)

For moderate versions:
Asus Eee Pad Transformer TF101 (4.0.3)
LG Lucid 4G (4.0.4)
HTC One S X520e (4.1.1)
Motorola Droid XYBOARD (10.1) MX617 (4.1.2)
Acer Iconia B1-A71 (4.2)
BQ Aquaris 5 HD (4.2.1)
HTC One mini M4 (4.2.2)

For the latest versions:
Samsung Galaxy Note II GT-N7100 (4.3)
LG Google Nexus 5 D821 (4.4)
HTC One M8 (4.4.2)
 
Conclusively, if want to win your game on Android app platform or marketplace, Android developer team of Mindinventory should be your exclusive choice.