To view parent comment, click here.
To read all comments associated with this story, please click here.
Nice theory, but it doesn't always work that way if either the API changes or an OEM does something odd to parts of their phone (Samsung, I'm looking at you). In these situations, an update is still needed. The app will only run on newer versions of the API so long as the API functions the app relies upon remain unchanged. You don't get support by default when changes occur.
http://developer.android.com/guide/topics/manifest/uses-sdk-element...
"Android applications are generally forward-compatible with new versions of the Android platform."
http://developer.android.com/guide/practices/compatibility.html
"whenever Android introduces new features or changes existing ones, we will always take steps to protect existing applications so that they don’t end up being available to devices where they won’t work."
To you have a prove, like a source/link, Samsung violates OHA agreement (http://www.zdnet.com/google-guarantees-android-compatibility-303929...) and the Android Compatibility Program (http://source.android.com/compatibility/index.html) or is that your own conclusion after looking at the different UI-theme?
Edited 2013-02-04 11:21 UTC




Member since:
2008-09-21
In which case the developer made the decision not to support API-level <14 cause eg the app/widget/service needs features that are only available in >13. Point is that decision is up to the dev. If the dev likes to support <14 then there is no reason to not AND all newer versions are supported out of the box.
Edited 2013-02-03 13:03 UTC