This document will analyze the potential volume increment in applications based on different development frameworks when integrating TUICallKit in detail.
TUICallKit Component Structure
TUICallKit Volume Increment Analysis
Taking TUICallKit 2.6.0 as an example, the following are the volume increments of applications output from each platform after integration with different development frameworks:
Android & iOS
|
Android | arm64-v8a | 16.2 MB |
| armeabi-v7a | 14.8 MB |
iOS | arm64 | 15.5 MB |
Flutter
|
Android | arm64-v8a | 14.9 MB |
| armeabi-v7a | 13.7 MB |
iOS | arm64 | 15.5 MB |
Note:
In the volume test on the Android platform, the compression feature for jniLibs and dex is enabled by default.
The volume increment data in this document is for reference only. The actual increment may vary due to factors such as plugin version, dependencies, build configuration, platform, and resource file. It is recommended to perform an actual build after integrating the plugin to obtain accurate data.
Was this page helpful?