On average, Crashlytics adds only 45kb - or the size of a single image - to the weight of your application.
We don't require linking against any additional frameworks or libraries.
When initialized at start-up, Crashlytics performs only a minimal amount of required work and defers the rest until a few seconds after app startup completes. This delay time is configurable -- we want your app to start as quickly as possible!
Our memory footprint has been carefully tuned to be the minimum necessary.
We care tremendously about the stability of your app and the experience for your users. If for any reason our SDK fails to do what it's supposed to do, it has no impact on your app or to your users.
We use run-time feature detection to ensure compatibility with Android 2.1 and beyond and iOS 4.0 and beyond.
All server communication is completed over SSL using packed-binary file formats. An average crash represents 20kb of data, which varies based on the length of your method names and the depth of the stack trace.
The first time a user launches your application, a single request is fired to our servers to configure the SDK’s behavior. The response is cached for later access and expired on a configurable time-period.
On the next execution after a crash occurs, binary data is POST’d to our servers.