▸Example Amplitude call (the "before")
import { Amplitude } from '@amplitude/analytics-react-native';
await Amplitude.init('YOUR_API_KEY', userId, {
trackingOptions: { ipAddress: true, language: true, platform: true },
});
await Amplitude.identify({
email: email,
plan: 'pro',
});
await Amplitude.track('Paywall Purchase', { value: price, currency: 'USD' });App-binary size affects download conversion (especially on lower-end devices and cellular networks) and storage pressure for users with full phones. Heavy analytics SDKs (Firebase Analytics, AppsFlyer, Branch) routinely add several MB to the binary; Respectlytics's per-platform SDK is under 100 KB.
☑Remove Amplitude cleanly
-
1
Remove the Amplitude SDK from your build (CocoaPods / SPM / Gradle / npm / pub)
-
2
Remove
Amplitude.initialize(...)andtrack(...)call sites — replace withRespectlytics.configure()andRespectlytics.track("event_name") -
3
Audit for
Identifyoperation usage — those set per-user properties; remove them -
4
If you used Amplitude Experiment for feature flags, plan a separate migration (e.g., GrowthBook or LaunchDarkly) — Respectlytics is analytics, not flagging
-
5
Confirm IDFA / AAID surfaces in your Info.plist + AndroidManifest are no longer needed by other SDKs before removing them
⇋Amplitude vs Respectlytics — smaller app binary
| Amplitude | Respectlytics | |
|---|---|---|
| Typical contribution to IPA size | — see tool note above | < 100 KB |
| Typical contribution to APK / AAB size | — see tool note above | < 100 KB |
| Transitive dependencies | — see tool note above | None (zero third-party) |
❓Frequently asked questions
How much do these SDKs typically add to my binary?
Varies by SDK. Rough order of magnitude on Android (release AAB): Firebase Analytics ~3-4 MB (with transitive Google Play Services), AppsFlyer ~1-2 MB, Branch ~1.5 MB, Mixpanel ~1 MB. Our [SDK Bundle-Size Comparator](/tools/sdk-bundle-size-comparator/) has up-to-date numbers per SDK.
Does binary size actually affect downloads?
Yes — particularly past Apple's 200 MB cellular-download cap and on lower-end Android devices with limited storage. Google's Play Console has internal metrics showing measurable install-rate differences when AAB size crosses common thresholds (50 MB, 100 MB).
How does the size reduction work in practice?
Removing a single ~3 MB SDK from your release build shrinks the binary by roughly that amount. Multiplied by user installs, the cellular-data savings compound. iOS App Thinning handles per-device variants; Android AAB delivers size-optimised installs by ABI / density / language.
Does the smaller SDK come at a feature cost?
Respectlytics intentionally doesn't bundle features it considers separate concerns: no ads, no attribution, no in-app messaging, no A/B testing, no crash reporting. Each of those is a dedicated tool's job. The smaller surface is the deliberate design — you add only what you actually use.