Background work, notifications, deep links, and app extensions
iOS decides when suspended apps receive background time. A request is an opportunity, not a timer guarantee. Work must be bounded, cancellable, resumable, and safe to repeat.
Design the boundary
- A BackgroundTasks adapter starts a sync use case, connects expiration to cancellation, reports completion, and submits future eligibility.
- Notification taps, universal links, widgets, intents, and share extensions parse input into the same validated route or command model.
- Extensions have separate targets, entitlements, memory limits, and available APIs. Keep them narrow.
- Local scheduling policy is testable. Remote delivery, token lifecycle, background timing, and extension execution need signed device evidence.
Validation boundary
No background launch, remote delivery, extension, account, or device run occurred.
Series navigation
- Previous: Part 81: Security, privacy, permissions, and platform policy
- Next: Part 83: Logging, analytics, crashes, privacy, and feature flags
- Series index: Zero to iOS Hero