▸Example GameAnalytics call (the "before")
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"
)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 GameAnalytics cleanly
-
1
Remove
pod 'GameAnalytics'fromPodfile -
2
Remove
implementation 'com.gameanalytics.sdk:gameanalytics-android-sdk:...'frombuild.gradle -
3
Remove
GameAnalytics.initialize(...)andGameAnalytics.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 — smaller app binary
| GameAnalytics | 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.