Replace Google Analytics for Firebase: fewer SDKs

Q: How do we audit our current dependency tree?

iOS: `swift package show-dependencies` (SPM) or `pod outdated` (CocoaPods) lists the tree. Android: `./gradlew :app:dependencies --configuration releaseRuntimeClasspath`. RN: `npm ls --all`. Flutter: `flutter pub deps`. Our [Dependency Privacy Scanner](/tools/dependency-privacy-scanner/) parses lockfiles from any of these and tells you which deps are forcing which privacy labels.

▸Example Google Analytics for Firebase call (the "before")

kotlin Respectlytics

import com.google.firebase.analytics.ktx.analytics
import com.google.firebase.ktx.Firebase

// GA4 event with user_id and freeform parameters:
Firebase.analytics.logEvent("level_up") {
    param("level", 7L)
    param("character", "Aragorn")
    param("user_id", userId)
}

Every third-party SDK is a supply-chain surface — manifest permissions, network endpoints, transitive dependencies. The biggest reduction in privacy footprint often comes from simply shipping fewer SDKs. Respectlytics has zero ads, attribution, or routing dependencies — it's one HTTPS endpoint.

☑Remove Google Analytics for Firebase cleanly

1
Remove the Firebase Analytics dependency from your build (CocoaPods / SPM / Gradle / npm / pub)
2
Remove the GA4 property's data stream linkage from your Firebase console — the data stops flowing as soon as the SDK is removed, but the property remains until manually deleted
3
Replace Analytics.logEvent call sites with Respectlytics.track("event_name")
4
Re-audit your Info.plist and AndroidManifest.xml for IDFA / AD_ID surfaces that GA for Firebase contributed
5
Confirm play-services-ads-identifier is no longer in the Android runtime classpath

⇋Google Analytics for Firebase vs Respectlytics — fewer third-party sdks

	Google Analytics for Firebase	Respectlytics
Direct ad / tracking dependencies	— see tool note above	Zero
Pulls Google Play Services	— typically yes	No
Auto-merged manifest permissions	Often (AD_ID, ACCESS_NETWORK_STATE, etc.)	None added
Number of HTTP endpoints contacted	Multiple (varies)	One (Respectlytics API)
Open-source SDK	— varies by tool	Yes (MIT-licensed)

❓Frequently asked questions

How do we audit our current dependency tree?

iOS: swift package show-dependencies (SPM) or pod outdated (CocoaPods) lists the tree. Android: ./gradlew :app:dependencies --configuration releaseRuntimeClasspath. RN: npm ls --all. Flutter: flutter pub deps. Our [Dependency Privacy Scanner](/tools/dependency-privacy-scanner/) parses lockfiles from any of these and tells you which deps are forcing which privacy labels.

What if we still need install attribution?

First-party alternatives without an SDK: Apple SKAdNetwork (iOS), AdAttributionKit (iOS 17.4+), Google Play Install Referrer API (Android). These are built into the OS — your ads platform reads them directly. No mobile SDK required.

What about crash reporting and push notifications?

Those are separate concerns with their own SDKs — Sentry / Crashlytics / Bugsnag for crashes; OneSignal / FCM / APNs for push. Respectlytics doesn't bundle them in; you pick the dedicated SDK for each surface.

Does shipping fewer SDKs measurably improve app size or cold start?

Often, yes — measurably. Removing Firebase + AppsFlyer + Segment from a typical RN app can shave several megabytes of bundle and 100-300ms off cold start. See the [SDK Bundle-Size Comparator](/tools/sdk-bundle-size-comparator/) for specific numbers.

⇢Related migration guides

Replace Google Analytics for Firebase to ship fewer third-party SDKs