apple-three-piece-analyticslisted

# Apple Three-Piece Analytics ## When to invoke - Starting a new App and deciding on an analytics SDK. - Evaluating Firebase / TelemetryDeck / Mixpanel / Amplitude / Sentry. - Writing `PrivacyInfo.xcprivacy`. - User asks "what metrics should I track", "what can I see without a third-party SDK". ## Scope Owns the source-selection decision and its PrivacyInfo/ATT consequence. Does NOT own MetricKit wiring or payload interpretation → `ios-performance-engineering`; sink code → `telemetry-facade-pattern`; App Review privacy-label parity → `app-store-review-rejections`. ## Default decisions ### v1 uses the Apple three-piece set | Source | What it provides | Where to view | |---|---|---| | **App Store Connect Analytics** | Downloads, sessions, active devices, retention, sources, store conversion | App Store Connect web | | **MetricKit** (`MXMetricPayload`, `MXDiagnosticPayload`) | Performance & diagnostics: crash / hang / launch time / jank / energy / memory | The App receives them → persist to log / optionally upload later | | **Game Center** (if it's a game) | Leaderboards / achievement completion / peer-player comparison | Game Center API / Game Center app | > **macOS caveat**: macOS 12–15 only send `MXDiagnosticPayload`; macOS 26 and later send a daily `MXMetricPayload` just like iOS. Only a deployment target below macOS 26 needs to fall back to App Store Connect Analytics + targeted `OSSignposter` traces. ### Privacy / Manifest - **`PrivacyInfo.xcprivacy` is a require