Logging, analytics, crashes, privacy, and feature flags
Production evidence should explain failures and product outcomes without collecting note content, credentials, precise location, or identity that the decision does not need.
Design the boundary
- Typed analytics cases prevent spelling drift and make every reviewed field visible.
- Logs diagnose one execution. Analytics answers defined product questions. Crash reports preserve stacks and binary identity.
- Keep matching archive symbols and redact sensitive breadcrumbs, request bodies, and note content.
- A feature flag has an owner, safe default, audience, expiry condition, and removal path. It never replaces authorization.
Validation boundary
No production analytics provider, crash service, remote configuration, or user dataset was connected.
Series navigation
- Previous: Part 82: Background work, notifications, deep links, and app extensions
- Next: Part 84: Instruments, responsiveness, energy, launch, and networking
- Series index: Zero to iOS Hero