android-discuss, How to stay backwards and forwards compatible - targetSDKVersion, hdpi, minSDKVersion?

 



Yes they will get them.  This specifies the minimum platform version the
resource is for.  (Note prior to 2.0 there was a bug where it was an exact
match, but that was fixed so you can count on -v4 and above working
correctly.)



It turns off the compatibility code for older applications that were not
written with 1.6 and later features in mind.  If you have tested against the
targetSdkVersion you have told the system you support, you will be fine.



You do if you want the system to run your app as well as possible on SDK 4
or later.



You can do that if you want.  It is up to you.  If you aren't using newer
APIs, it is not required.



targetSdkVersion should not impact that.

-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

--

 


The worst bug I've had so far in Android development was an out of
memory that showed up when I used targetSdkVersion="X".  It took quite
awhile to figure out that was the culprit, and when I removed it I
didn't see any out of memory problems at all.  The problems showed up
on the Motorola Droid, late last year.   I spent a lot of time
optimizing my own memory usage to try and fix it, but removing
targetSdkVersion="X" worked best.

My 2 cents,
-MK

--