App size
What the SDK adds to your app, per platform. The editor, preview, export, text rendering and effects all run on the same engine, so the size is mostly one native library (one wasm file on the web) and doesn't grow with the features you use.
| Platform | Added on the device | Added to the download |
|---|---|---|
| iOS (arm64) | 12.5 MB | ~12.5 MB |
| Android (arm64-v8a) | 13.8 MB | ~6.1 MB |
| Android (armeabi-v7a) | 9.8 MB | ~5.5 MB |
| Web | 8.9 MB wasm, ~0.1 MB JS | 1.9 MB (brotli), 2.7 MB (gzip) |
Measured on release builds of version 0.1. Numbers are updated with each release.
Why the download differs from the size on the device
- iOS: the App Store encrypts app code, and encrypted code doesn't compress, so the download grows by about as much as the app on the device. Simulator architectures are never shipped to users.
- Android: Google Play delivers only the library for the device's CPU and compresses the download. Publish an Android App Bundle (the default for Play) so users don't download the libraries for other CPUs.
- Web: the wasm file is downloaded once and cached by the browser. Serve it with brotli or gzip compression, and from the same version URL across releases of your app, so returning users don't fetch it again. Export runs the same file in a worker; it's loaded from the cache.
React Native
The same as iOS and Android above, plus less than 0.5 MB for the bridge and JavaScript.
Keeping it small
- Android: with an App Bundle, each device gets only its own library. If you ship APKs directly, arm64-v8a covers almost all phones; add armeabi-v7a for older 32-bit devices and x86_64 only if you target Chromebooks.
- iOS: nothing to do; the framework is dynamic and App Store thinning keeps only the device slice.
- Web: load the editor when the user opens it rather than on your app's first page, so the rest of your app doesn't wait for it.