Client SDK App Size
How much will it add to my app?
This is measured automatically for every release, by building a minimal app twice — once with the SDK, once without — and taking the difference. It is the number your users feel, not the size of what you download at build time.
| Platform | Download size added | Installed size added | SDK version |
|---|---|---|---|
| Android (App Bundle, arm64-v8a) | +12.15 MB | +19.90 MB | 2.11.2 |
| iOS (App Store, arm64) | +17.53 MB | +31.69 MB | 2.11.2 |
Download is what your users transfer when installing. Installed is what it occupies on the device afterwards, which is larger because the download is compressed.
iOS is the larger of the two, and not because the SDK is different there: Android delivers one prebuilt native library per device and R8 removes the Kotlin layers your app never calls, while on iOS the media engine is linked into your binary and the SDK's Kotlin core is a framework that ships whole.
Your figure will differ, usually downwards
The reference app is empty apart from the SDK, so this is close to a worst case. If your app already ships anything the SDK also needs — Kotlin's standard library, for instance — you pay for it once, not twice.
Where those bytes go
| Component | Why it's there |
|---|---|
| WebRTC | the media engine: audio pipeline, echo cancellation, jitter buffer, DTLS/SRTP, ICE. Required for any call. |
| Noise suppression | an ML model plus its native runtime. Bundled today; making it optional is planned, and it is the largest single saving available. |
| Client SDK | session, signalling, call control, public API. A small fraction of the total. |
Almost none of it is Vonage's own code — the SDK is a thin layer over a large media engine, and no build configuration removes the parts a voice call needs.
Reducing it
Android: publish an App Bundle. A universal APK carries every ABI — four copies of the engine, when a device can use exactly one. Switching is a distribution change with no code impact, and it is by far the largest saving available to you.
iOS: nothing to do. The App Store delivers one architecture per device automatically, and the figure above already reflects it. There is no equivalent of the App Bundle switch — the SDK's Kotlin core ships as a dynamic framework that is embedded whole, and the installation guide's required -ObjC linker flag deliberately keeps the Objective-C classes the linker would otherwise discard. Both are necessary, and the figure above is measured with them in place.
See Reducing App Size on Android and on iOS for detail, and ProGuard Rules if you enable R8.
Why the download is so much bigger than this
Worth knowing, because it surprises people: the iOS artifact you fetch at build time is several times the figure above. Most of it never reaches a device — roughly half is C++ headers your compiler reads and debug symbols for symbolising crash reports, and the architectures you don't ship are dropped at export. On Android the SDK ships a prebuilt shared library per ABI, so nothing is stripped, but only one ABI is delivered.
So don't read anything into the size of the artifact itself — the figure above is the one that reaches your users.