Replace GameAnalytics: RAM-only events

Q: What's the actual flush cadence?

30 seconds by default, plus a flush on `applicationDidEnterBackground` (iOS) / `onPause` (Android). Most events reach the network within seconds of being fired.

▸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"
)

Most analytics SDKs back the unsent event queue with SQLite or UserDefaults / SharedPreferences — so a phone that's been confiscated, jailbroken, or restored from backup still contains analytics state. Respectlytics's queue is RAM-only, flushed on a 30-second timer; unsent events on force-quit are lost by design, in exchange for zero on-device forensic surface.

☑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 — ram-only event queue

	GameAnalytics	Respectlytics
Event queue persistence	SQLite / UserDefaults / SharedPreferences	In-memory ring buffer
Disk usage for analytics	0.5–10 MB typical	0 bytes
Forensic data on jailbroken / rooted devices	Persistent identifiers + queued events	None
Survives force-quit before flush	Yes	No (events lost — by design)

❓Frequently asked questions

Doesn't this reduce data quality?

Marginally — typical force-quit-before-flush event loss is 0.5–2% depending on platform. For aggregate metrics (funnel rates, feature adoption, release deltas) this is invisible. For per-event reconciliation it would be a problem, but per-event reconciliation isn't a use case Respectlytics supports.

What's the actual flush cadence?

30 seconds by default, plus a flush on applicationDidEnterBackground (iOS) / onPause (Android). Most events reach the network within seconds of being fired.

Is this safe for crash analytics?

Crash analytics is a separate concern — use Sentry, Crashlytics, or Bugsnag (with their own crash-aware queues). Respectlytics is product analytics; crash data has different recoverability requirements and lives in different tools.

Why is this a privacy feature?

Devices that are jailbroken, rooted, restored from backup, or forensically imaged routinely surface analytics artifacts — distinct_ids, queued events, user properties — that survive uninstall in some cases. RAM-only storage moves the dump-recovery surface to zero.

⇢Related migration guides

Replace GameAnalytics with a RAM-only event queue