You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our release APK has a size of roughly 11 MB. The libsigner.so (uncompressed) alone is about 950 KB (for arm64-v8a). So the native library from Adjust Signature SDK causes a significant amount of the app size.
Thanks for getting in touch & sharing your thoughts.
I can confirm that the size is an outcome of the product's nature: The Signature is a highly obfuscated library and aims to thwart both dynamic and static analysis. Some of those traits lead to an increase in size.
The above said, we are not disregarding the impact on an app in the name of security. Indeed, the size is a major point of discussion before every release and with considerable work in the past to minimize. It's, however, often a tradeoff between the product's defenses and size.
Given the current status quo with fraud, I cannot promise alterations as that would damage the product's defenses. But I can confirm continuous monitoring and effort to keep the size at bay. Naturally, we will go through the link you shared and similar in detail to see if something was missed on our end.
Our release APK has a size of roughly 11 MB. The libsigner.so (uncompressed) alone is about 950 KB (for arm64-v8a). So the native library from Adjust Signature SDK causes a significant amount of the app size.
We can not evaluate how much effort you already put into optimizing binary size. Maybe there is still some room for improvement, like e.g. these technics: Android NDK: How to Reduce Binaries Size – The Algolia Blog
The text was updated successfully, but these errors were encountered: