the Android Market and Compatibility
by Dave Loft
I’ve been mulling this over for the past week and wanted to share my thoughts on it. Ultimately what it comes down to is that there is no guarantee that the games your buying for your Android phone today are going to work on your next Android device. More apps and games are being targeted at specific devices. At Google IO in the market session it was mentioned that developers would now have even more control over which which device can access the game by not only chipset, screen size and android version but also the specific model.
So now a developer can build a compatible list or a not compatible list. An example of each that recently hit the market is the Netflix app which is limited to work on only five devices and Battleheart which currently blocks many Samsung and HTC devices. The worst part of this is that as the hacking community has shown running a rooted android with the hacked Netflix app can work on just about any device.
Blocking a specific model can result in blocking devices that may have been updated or are running custom software that actually fixes the issue that the device was blocked for. To take it even further a device may be blocked due just to performance issues. Something that a rooted device with a stock ROM running an overclocked CPU can often fix.
Ultimately these updates are great for the average Android user as it will reduce the number of times they will come across apps and games that do not work on their device. But it’s the power users that will ultimately have run into challenges from these changes.
Jump ahead one or two years after your first Android and you may find yourself in a situation where many of the games you have wont work on your brand new device. This will be especially true for anyone who owns a Tegra 2 based device or the Xperia Play. With so many games being made specifically just for those devices if your next device is not a Tegra device or the Xperia Play 2 it won’t work.
This also extends to any 3D game that specifically lists what devices it works on. Next year if you go and buy the latest and greatest phone that should easily be able to handle the game but the developer hasn’t added it to the list of compatible devices. As a result it won’t even show up in the market for you.
So going forward the argument that because it’s an Android device and you bought it from the Market doesn’t give you any guarantee. It kind of puts some perspective on the many arguments against buying from Gameloft because it won’t work on your next device. As it is, no matter where you buy it, there really is no guarantee it will work.
Google also introduced another update to the market, but this one could help alleviate many issues. They will allow a developer to have one listing for their game and it can hold multiple APK’s. This would be helpful for example if you currently own a Tegra 2 device, you would be given the Tegra 2 version. Then for example next year you buy the Xperia Play 2 and then when you hit the market to download your apps you would be given the appropriate version.
Unfortunately by the looks of things in the market this may be more of a dream than a reality. Many Tegra 2 games won’t work on any other platform and the one’s that do like Fruit Ninja and Guerrilla Bob have a higher price for the Tegra 2 version.
Thankfully most developers seem to have the right idea by just adding support to the Xperia Play in the regular version of the game. But I have to give a thumbs down to any developer choosing to build a separate version for the Xperia Play.
Now before you get too worried about all this just bear in mind this is really only going to affect more advanced 3D games. Most apps and games should work just fine. This issue could also be helped if Google takes a stronger stance and more aggressively enforces the Android Market. The biggest thing Android needs is an all encompassing graphic layer akin to DirectX. This would alleviate the need for developers to write for specific chipsets and would greatly help eliminate compatibility issues. Going forward hopefully developers and Google don’t let things get too far out of hand.