Following up a post on the Android Developer blog, TechCrunch writes about the possible problems deriving from caring about backward compatibility:

As an open platform, Google isn’t requiring backward compatibility for all Android apps. But as more devices and applications come out, that could be an issue. As Google writes, “do you want to allow your application to run on all devices, or just those running newer software?” Plenty of iPhone apps answer that very question with the latter. And while you might think that may be limiting, it ensures a certain level of simplicity in the App Store — and perhaps more importantly, in developing for the iPhone.

The iPhone platform already has a massive lead in terms of applications built for it over Android. Anything, such a backwards compatibility code, that adds complexity to developing for Android is certainly not going to help.

While I can not see the benefit for the user in having non backward compatible applications, I fully agree that setting backward compatibility as standard expectation for Android applications will make it even harder for Android developers.

This adds up to the complexity of not being able to know the hardware specifications your application will run on, which I wrote about in my post “Is Android’s Flexibility a Disadvantage?”.

One Response to “Android Backward Compatibility”


  1. [...] 11, 2009 Following up my recent post on Android Backward Compatibility, the same problem seems to strike back to iPhone developers now. As Ars Technica reports, many [...]


Leave a Reply