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

swift Respectlytics

import GameAnalytics

GameAnalytics.configureBuild("1.0.0")
GameAnalytics.initialize(withGameKey: "YOUR_KEY", gameSecret: "YOUR_SECRET")

GameAnalytics.addProgressionEvent(
    withProgressionStatus: GAProgressionStatusComplete,
    progression01: "world_1",
    progression02: "level_5",
    score: 1200
)
GameAnalytics.addBusinessEvent(
    withCurrency: "USD",
    amount: Int32(priceInCents),
    itemType: "iap",
    itemId: sku,
    cartType: "main_paywall"
)

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

1
Remove pod 'GameAnalytics' from Podfile
2
Remove implementation 'com.gameanalytics.sdk:gameanalytics-android-sdk:...' from build.gradle
3
Remove GameAnalytics.initialize(...) and GameAnalytics.addBusinessEvent(...) call sites
4
Replace progression and resource event call sites with Respectlytics.track("event_name") using distinct event names per level / resource type
5
If you used GameAnalytics's benchmark comparisons as a product KPI, plan how you'll source those numbers post-migration

⇋GameAnalytics vs Respectlytics — fewer third-party sdks

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