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". ## 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 | > **macOS caveat**: MetricKit on macOS yields a reduced payload set compared to iOS (some payload types are iOS-only, e.g. `MXAppLaunchMetric`). For mac-heavy apps, lean more on App Store Connect Analytics + targeted `OSSignposter` traces. | **Game Center** (if it's a game) | Leaderboards / achievement completion / peer-player comparison | Game Center API / Game Center app | ### Privacy / Manifest - **`PrivacyInfo.xcprivacy` is a required deliverable** (hard App Store submission requirement). - Because no third-party SDK, no IDFA, no PII are collected, the manifest content is very minimal. - **No ATT prompt needed** (no IDFA use case). - CloudKit / Game Center's user-facing privacy notices are handled at the system layer b