Android

An exercise in fragmentation: Limiting Android installs to device models

As if there were not enough fragmentation issues with Android, app makers go out and make it worse when they limit installations to specific devices.

Here I sit, with a barely six-month-old Galaxy S4, and yet I cannot use an app available for the device, because the version of the S4 that I have is the S4 Active, Samsung's latest waterproof phone.

It's one of the grating issues I have with using an Android device. Despite all of the good work that Google has done to subdue the problems that developers encounter with fragmentation, a certain type of device and app maker is determined to divide and conquer Android, a handful of devices at a time.

In the past two days, a pair of apps with device restrictions have appeared in the Play Store: The long-awaited Android version of the Australian Broadcasting Corporation's iView app, and Foxtel's Go app.

What is simultaneously interesting and frustrating is that rather than restricting the deployment of the apps by Android version number or screen resolution, both have taken the path of only allowing certain devices to install it with the use of a whitelist.

For why this is an issue, just look at the lovely list of devices in the Play Developer Console that appear when a search for "S4" is conducted.

s4-play-console.png
The problems kick into gear when you realise that Samsung treats "S4" as both a device name and an overall term for a collection of devices. Not only does the company make a "Samsung Galaxy S4", but it also sells a "Samsung Galaxy S4 Active", "Samsung Galaxy S4 Zoom", "Samsung Galaxy S4 Mini", "Samsung Galaxy S4 Google Play Edition", and a "Samsung Galaxy S4 Duo", as well as having a motley collection of model numbers.

So when an app maker says its app is supported on the Galaxy S4, maybe it is, and maybe it isn't. In the case of the ABC app, after an initial refusal, about an hour later, the app was allowed to be installed on my S4. As for the Foxtel app, despite having all the performance and other requirements to run the app, I was refused by Foxtel's device whitelisting.

Upon asking why it allows one S4 model and not another, Foxtel responded by saying, "each Android device behaves differently and needs to be checked to ensure it provides the right Foxtel experience and that content is delivered securely".

Despite the app having Samsung exclusivity, the company said it would "love to get Foxtel Go on as many devices as possible and are working hard to do so".

Making decisions on app availability based on phone models is not the right way to go about Android app development, and does nothing to help the Android ecosystem.

What is the point of having a homogeneous platform span across many different devices if apps are going to ignore suitable devices that are capable of using them?

It would make little sense in the PC world to restrict an app to only Lenovos or HP computers, and it makes just as little sense in the mobile world.

About

Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic advent...

2 comments
eniyeu
eniyeu

You have chosen this particular grief. Do what I do. Purchase only Nexus devices, and/or the GooglePlay editions of same.  Applications that won't load on those I don't care for.  The OEMs and Software authors would take note, and very quickly too if enough people voted with their wallets instead of whining.  You think they actually listen or care for anything else?  If it's not the ”bottom line” then it's just NOISE.  The sooner you grasp that, the sooner you will stop making noise!

eniyeu
eniyeu

You have chosen to have this grief. Do what I do. Purchase only Nexus devices, or the GooglePlay editions of. Whatever applications don't load on those, I am not interested in. The OEMs and application authors would get the message, and very quickly too.