Apps Old Codes and min- and targetSdkVersion

[ac4android]

I am looking thru some old codes at the moment.

I noticed that in some of the really big apps, they have a lot of settings in the AndroidManifest.XML which I put in the module build.gradle, for example, these are in the 3rd party Manifest :

android:versionCode="2"
android:versionName="Tooth Fairy"
<uses-sdk
android:minSdkVersion="7"
android:targetSdkVersion="10" />

These codes also use android:glEsVersion="0x00020000"
I was wondering whether I should upgrade that to "0x00030001" without impacting on the codes downstream somewhere.

As you can see, pretty old codes going by the versions.

Wouldn't it be nice if Google has a book that explains everything in A/Studio.


ADDENDUM: They are very good codes, even I understand them, but it seems A/S has changed a lot since they were written and I am struggling with A/S functionalities rather than the codes.

 

[Deleted User]

Well you could upgrade the library version, but chances are it would break the code. Quite often library APIs are deprecated or changed, which means any dependent code must also change.
If there is no real reason to upgrade, and everything works, then don't.

 

[ac4android]

That's good advice, I think I'll stick with the old codes, they have all the old .jar and .so packaged into /app/libs. It'll take a huge effort to update codes.

I think that answers my other question about the gradle wrapper. It's impressive, whoever did that.

Thanks.