Controlling APK Size When Using Native Library

Transcript

1. Controlling APK Size When Using Native Library
2. I am Brijesh Masrani @
3. Outline • What are the major components in APK? • APK Splitting • What is ABI and how it works? • Understanding ABI in detail • Problems with ABI split • Solving Issues with abiFilters
4. What are the major components in APK? • Class files • Resources • Manifest file • Native libraries
5. APK Splitting Density and Application Binary Interface (ABI)
6. Application Binary Interface • The ABI defines, with great precision, how an application’s machine code is supposed to interact with the system at runtime. • You must specify an ABI for each CPU architecture you want your app to work with. • mips, mips64, X86, X86–64, arm64-v8a, armeabi, armeabi-v7a
7. Analysis of the APK file
8. APK details after adding Realm
10. Realm distribution for different CPU architecture
11. Realm adds .so file for 5 CPU architectures mips, X86, X86–64, armeabi-v7a, and arm64-v8a this increases the apk size by 4.8 MB; remaining ~130KB is increased in dex size.
12. ABI split
14. Multiple APK files generated after enabling split
16. Amazing right! We went from 74KB to 5MB and came back to 1.3 MB. But But But….
17. NDK abiFilters
18. APK with “armeabi-v7a” and “x86” libs
19. TL;DR — Detail about CPU Architecture
20. Google Maps with ABI filters
22. Thank You You can find me at @brijeshmasrani