▸Example Firebase Analytics call (the "before")
import FirebaseAnalytics
// Default Firebase event with rich per-user metadata:
Analytics.logEvent("purchase", parameters: [
"value": price,
"currency": "USD",
"transaction_id": UUID().uuidString,
"user_id": userId,
])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 Firebase Analytics cleanly
-
1
Remove
pod 'Firebase/Analytics'fromPodfile(and anyFirebase/Corepulled by it that isn't needed elsewhere) -
2
Remove
implementation 'com.google.firebase:firebase-analytics-ktx'frombuild.gradle.kts -
3
Remove
@react-native-firebase/analyticsfrompackage.json -
4
Remove
firebase_analytics:frompubspec.yaml -
5
Remove
FirebaseApp.configure()andAnalytics.logEventcall sites — replace withRespectlytics.configure()andRespectlytics.track("event_name") -
6
Delete the
GoogleService-Info.plistandgoogle-services.jsonif no other Firebase product remains in the app -
7
Run
./gradlew :app:dependenciesand confirmplay-services-ads-identifieris no longer in the runtime classpath
⇋Firebase Analytics vs Respectlytics — smaller app binary
| Firebase Analytics | 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.