▸Example Matomo Mobile call (the "before")
import MatomoTracker
let tracker = MatomoTracker(siteId: "1", baseURL: URL(string: "https://your-matomo.example.com/matomo.php")!)
tracker.userId = userId
let event = Event(
tracker: tracker,
action: ["purchase"],
eventCategory: "ecommerce",
eventAction: "purchase",
eventName: "paywall",
eventValue: NSNumber(value: price).floatValue
)
tracker.track(event)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 Matomo Mobile cleanly
-
1
Remove the Matomo SDK from your build (
MatomoTracker/org.matomo.sdk:tracker/matomo_tracker) -
2
Remove
Tracker.builder().build()initialisation andtrack(...)call sites -
3
Decide whether your Matomo server stays online (for web traffic) or gets decommissioned
-
4
If you used Matomo's visitor segments alongside web data, plan how you'll bridge web ⇄ mobile analytics under Respectlytics (web isn't Respectlytics's primary surface)
⇋Matomo Mobile vs Respectlytics — faster cold start
| Matomo Mobile | 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.