Replace Amplitude: 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 Amplitude call (the "before")

js Respectlytics

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' });

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 Amplitude cleanly

1
Remove the Amplitude SDK from your build (CocoaPods / SPM / Gradle / npm / pub)
2
Remove Amplitude.initialize(...) and track(...) call sites — replace with Respectlytics.configure() and Respectlytics.track("event_name")
3
Audit for Identify operation 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 — fewer third-party sdks

	Amplitude	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 Amplitude to ship fewer third-party SDKs