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

swift Respectlytics

import Flurry_iOS_SDK

let builder = FlurrySessionBuilder.init()
    .withAppVersion("1.0")
    .withLogLevel(FlurryLogLevelAll)
    .withCrashReporting(true)
Flurry.startSession(apiKey: "YOUR_FLURRY_KEY", sessionBuilder: builder)

Flurry.log(eventName: "Purchase", parameters: [
    "user_id": userId,
    "value": String(price),
    "currency": "USD",
])

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

1
Remove pod 'Flurry-iOS-SDK/FlurrySDK' from Podfile
2
Remove implementation 'com.flurry.android:analytics:...' from build.gradle
3
Remove react-native-flurry-analytics from package.json if used
4
Remove Flurry.builder().build(...) initialisation and Flurry.logEvent(...) call sites
5
If you used Flurry's Configuration Provider for remote config, plan a separate migration (e.g., Firebase Remote Config, GrowthBook)
6
Delete the Flurry app entry once events stop flowing (the dashboard may already be sunset by the time you migrate)

⇋Flurry vs Respectlytics — ram-only event queue

	Flurry	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 Flurry: no att prompt Same tool, No ATT prompt Replace Flurry: no pii collected Same tool, No PII collected Replace Flurry: no phi collected Same tool, No PHI collected Replace Flurry: 5-field event schema Same tool, 5-field event schema Replace Flurry: fewer third-party sdks Same tool, Fewer third-party SDKs Replace Flurry: smaller app binary Same tool, Smaller app binary Replace Flurry: faster cold start Same tool, Faster cold start Replace Flurry: eu data residency Same tool, EU data residency Replace Flurry: self-hosted deployment Same tool, Self-hosted deployment Replace Flurry: open-source sdk + server Same tool, Open-source SDK + server Replace Firebase Analytics: ram-only event queue Same outcome, Firebase Analytics Replace Google Analytics for Firebase: ram-only event queue Same outcome, Google Analytics for Firebase

Replace Flurry with a RAM-only event queue