Respectlytics Respect lytics
Menu
Replace Branch Fewer third-party SDKs

Replace Branch to ship fewer third-party SDKs

Migrate from Branch to Respectlytics to reduce your dependency tree. Helps developers avoid collecting personal data.

Example Branch call (the "before")

swift Respectlytics
import BranchSDK

Branch.getInstance().initSession(launchOptions: launchOptions) { params, error in
    // Branch fingerprint + IDFA matching happens here.
    if let referringLink = params?["~referring_link"] as? String {
        // Route the user based on the deep link...
    }
}

Branch.getInstance().userCompletedAction("Paywall Purchase", withState: [
    BranchStandardEventTransactionId: orderId,
    "revenue": price,
])

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

  1. 1

    Remove Branch from your build (Branch / io.branch.sdk.android:library / react-native-branch / flutter_branch_sdk)

  2. 2

    Remove Branch.getInstance().initSession(...) and userCompletedAction(...) call sites

  3. 3

    Decide what replaces Branch's deep-link routing — Universal Links + App Links are first-party alternatives (no SDK; OS-handled)

  4. 4

    Remove Branch URL schemes from your Info.plist and AndroidManifest.xml

  5. 5

    Delete the Branch app dashboard entry once events stop flowing

Branch vs Respectlytics — fewer third-party sdks

BranchRespectlytics
Direct ad / tracking dependencies— see tool note aboveZero
Pulls Google Play Services— typically yesNo
Auto-merged manifest permissionsOften (AD_ID, ACCESS_NETWORK_STATE, etc.)None added
Number of HTTP endpoints contactedMultiple (varies)One (Respectlytics API)
Open-source SDK— varies by toolYes (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

Track what matters. Collect nothing you don't.

Five-field event schema, RAM-only event queue, no IDFA, no AAID, no persistent user IDs. Helps developers avoid collecting personal data in the first place.