This message was deleted.

You can create a configuration, add one dependency to it, and then look at its files and their size. Repeat for the other library, and compare.

although that might not be the actual size increase, because if it's sharing libraries you're already depending on, then that's effectively free

although that might not be the actual size increase, because if it's sharing libraries you're already depending on, then that's effectively free

ok I can run it in a new project where I add only the dependency which I wanna measure.

I would simply try adding each the library then measuring your project's build size

Good alternative: with build size you mean the size of the apk?

if you're talking about an Android app, then the size of the .aab or .apk, yes. the size of the JARs is not very representative because your release build will get proguarded

Doesn't the apk get proguraded too?

release apk, usually yes. debug apk, usually not

ahh ok

note that you'll actually have to make use of the library otherwise proguard will see all of it as unused and drop it

Can I disable it?

yes, but then the sizes you get will not be similar to the sizes you'll get when you actually use the library, so it's not very useful

I'm just interested in the absolute size of the lib and its deps, so I guess it's negligible

why do you care about that? shouldn't what matter be the size of the part of the lib that you actually need when proguard retains it?

hmmm I know what you mean, makes sense, thanks for the insight. But then I would have to write code for every library, that's not worth the time

Well, then you probably should not choose by size 🙂