▸Example Singular call (the "before")
import com.singular.sdk.Singular
import com.singular.sdk.SingularConfig
val config = SingularConfig("YOUR_API_KEY", "YOUR_API_SECRET")
config.withIMEICollection()
Singular.init(applicationContext, config)
Singular.event("sng_purchase", JSONObject().apply {
put("revenue", price)
put("currency", "USD")
put("user_id", userId)
})Heavy analytics SDKs do work at app launch — reading identifiers, initialising queues, network dispatch — that compounds visibly on lower-end devices. Respectlytics's SDK adds typically under 30ms to cold start, vs 100-300ms for Firebase Analytics's full initialisation chain.
☑Remove Singular cleanly
-
1
Remove the Singular SDK from your build (
Singular-SDK/singular_sdk/singular-react-native) -
2
Remove
Singular.start(YOUR_API_KEY, YOUR_API_SECRET)andSingular.event(...)call sites -
3
Decide ATT posture — remove
NSUserTrackingUsageDescriptionif Singular was the only ATT-triggering SDK -
4
Remove the AD_ID permission from the Android merged manifest if no remaining SDK contributes it
-
5
Plan SKAdNetwork + Google Play Install Referrer as the first-party attribution replacement
⇋Singular vs Respectlytics — faster cold start
| Singular | Respectlytics | |
|---|---|---|
| Typical cold-start contribution (p50) | — see tool note above | < 30ms |
| Initialisation work on launch | Reads IDFA/AAID, opens SQLite, spins up threads | Allocates ring buffer (RAM-only) |
| Number of background threads spawned | — typically 2-4 | 1 |
| Synchronous I/O on init | — typical (SQLite open) | None |
❓Frequently asked questions
How do I measure cold start before / after?
iOS: Xcode Organizer's Launch Time metric (aggregate from real users) or Instruments → App Launch template (synthetic). Android: adb shell am start -W <package>/.<activity> or Play Console's Vitals → Startup time. Measure before removing the old SDK, after, and compare on the same device class.
Does Respectlytics block the main thread on init?
No. Respectlytics.configure(appKey:) is synchronous but does only in-memory work (allocates the ring buffer). The network flush runs on a background dispatch queue / coroutine.
What's typical magnitude of improvement?
On a mid-range Android device, removing Firebase Analytics + AppsFlyer typically saves 100-300ms off cold start, depending on Google Play Services init state. On iOS the delta is usually 50-150ms. Effect is more pronounced on cold-start (uncached) than warm-start launches.
Does cold-start improvement actually affect business metrics?
Yes — first-session abandonment correlates with launch latency in published benchmarks. A 100ms improvement on the slowest deciles of your device distribution can show a measurable first-day retention lift.