As I pointed out in my previous article, the need to be actively present on the mobile market is more than obvious. In the United States, Android continues to make progress with 51.7% on the American smartphone sales market (according to Kantar Wordpanel Comtech) compared to 41.4% registered by iOS and 5.6% by Windows. This difference is even more striking at European level with 70.4% of Android smartphones (also according to Kantar Wordpanel ComTech).
In 2013, Android runs on 867 million devices across all platforms (Smartphones and tablets), and it is expected to reach 1 billion in 2014. Given such figures, it becomes almost mandatory to create or port your application to Android.
These devices are created under many different models. They vary in display size, processing power, communication capabilities (2/3/4G, NFC, Wifi, BT…), multimedia capabilities (graphic processor, camera, sounds…) and in the upper layer specific to each manufacturer. Needless to say that each model is unique as the manufacturers use specific drivers in order to make the most of the platform.
If you are also developing Android applications, as we currently are, you will quickly struggle with this diversity of physical platform models that OS Android has yet to standardize. This triggers higher costs for your development project, since the number of tests to perform (as compared to iOS for instance) is multiplied by the number of target models. You have to make sure that your application runs on all devices, and that you avoid a negative brand image. This requires regular technological watch on the popular models and their drivers, good mastering of Android layers and good targeting of the most used models (or those you are aiming at as they have a particular capability you want to use such as Bluetooth, a HD camera, or simply a keypad).
Check our testimonials: offshore product testing