Replace Flurry: open-source

Q: Where can we audit the source?

GitHub: `github.com/respectlytics`. Each SDK has its own repository with source, tests, CI configuration, and release tags. The server lives in a separate repo with the same conventions.

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

Closed-source analytics SDKs require you to trust vendor claims about behaviour. Open-source SDKs let your security team verify those claims from source. For regulated industries this is often a procurement-gating requirement. Respectlytics's SDKs are MIT-licensed and fully open; the server is AGPL-3.0.

☑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 — open-source sdk + server

	Flurry	Respectlytics
SDK source publicly available	— see tool note above	Yes (MIT)
Server source publicly available	— typically no	Yes (AGPL-3.0)
Reproducible builds from source	— varies	Yes (CI publishes from same commit)
Fork-and-modify allowed	— varies by license	Yes
Public commit history	— typically no	Yes (GitHub)

❓Frequently asked questions

Where can we audit the source?

GitHub: github.com/respectlytics. Each SDK has its own repository with source, tests, CI configuration, and release tags. The server lives in a separate repo with the same conventions.

Are the published binaries reproducible from source?

Yes — CI builds use deterministic build commands. The artifacts published to CocoaPods / SPM / Maven Central / npm / pub.dev are produced by the same pipeline that runs against each commit. Reproducible builds are a goal we test against; report any discrepancy as an issue.

Can we modify the SDK and ship our fork?

Yes — MIT permits modification and redistribution with attribution. Many enterprises fork to adjust logging, add internal tracing, or vendor the SDK into their build.

Why MIT for SDK and AGPL for server?

Standard split for source-available SaaS (GitLab, Sentry, MinIO, Plausible). MIT on the SDK maximises consumer freedom — your app picks up the dependency without obligation. AGPL on the server prevents competing closed-source SaaS forks while allowing internal self-hosting freely.

⇢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: ram-only event queue Same tool, RAM-only event queue 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 Firebase Analytics: open-source sdk + server Same outcome, Firebase Analytics Replace Google Analytics for Firebase: open-source sdk + server Same outcome, Google Analytics for Firebase

Replace Flurry with an open-source analytics stack