Android targetSdkVersion行为

Question

I am confused about the requirement/behavior of targetSdkVersion . As far as I understood, setting the target SDK to a particular version indicates that behavior of the application (UI) is ensured up-to that particular version.

In my application, I had set my targetSdkVersion to 1 (for testing) and I have some buttons in my page. What I expected was, there will not be any ripple effects in button click (which was introduced in later versions of Android). But there was a ripple effect when I clicked the button.

Application was running on lollipop .

Can any one explain how this works.

Answer 1

There are three SDK levels of note:

• targetSdkVersion : this is a hint to Android of what version the app is designed to run on. An example of it relevance is that if you set targetSdkVersion to 22 then android will not enforce permissions introduced in version 23 ... and if you up targetSdKVersion to 23, android takes this as an indication that you app knows how to handle system permission requests.

• minSdkVersion : the minimum version (that you say) you app will run on. play will not show the app to users on a lower version.

• compileSdkVersion : this is the version your app is compiled against. You need to download the relevant SDK to build against. This is the variable the would have the effect you expect in the example above. As the relevant system apis wont be available to your app.

Answer 2

The targetSDK in my opinion will not matter the behavior of your app.It is just the API level and does not deal with the user Interface part.

An integer designating the API Level that the application is targetting.

With this attribute set, the application says that it is able to run on older versions (down to minSdkVersion), but was explicitly tested to work with the version specified here. Specifying this target version allows the platform to disable compatibility settings that are not required for the target version (which may otherwise be turned on in order to maintain forward-compatibility) or enable newer features that are not available to older applications. This does not mean that you can program different features for different versions of the platform—it simply informs the platform that you have tested against the target version and the platform should not perform any extra work to maintain forward-compatibility with the target version.

Hope this helps mate!!Cheers Happy Coding