17.1 · UserNotifications, APNs and how a push actually gets delivered
Notifications are the one system feature users judge your whole app by. The framework is small; the traps are permission timing, what you cannot control, and how Apple’s push service decides to deliver.
Mental model. A notification is a request to the system, not a guarantee. The user, the OS and APNs each get a veto.
Local and remote notifications
Authorization, triggers, categories and actions.
- How do local and remote notifications work with UserNotifications: authorization, triggers, categories, and interruption levels?
Everything goes through UNUserNotificationCenter.current(). First authorization: requestAuthorization(options:) (alert, sound, badge, and optionally…
The push path
APNs, priorities, collapsing and delivery guarantees.
- How does the Apple Push Notification service deliver a push: tokens, priority, collapse, expiry, and what can go wrong?
A remote notification travels provider (your server) → APNs → device → app. At launch the app calls registerForRemoteNotifications(); the system obtains a…
More in System frameworks
- 17.2 · Core Location and MapKit
- 17.3 · Contacts, Calendar, Photos, HealthKit and Core Motion
- 17.4 · CloudKit, StoreKit 2 and PassKit
- 17.5 · AuthenticationServices and passkeys, Spotlight, Handoff and user activities
- 17.6 · Live Activities, WeatherKit, App Clips and CarPlay
- 17.7 · A checklist for learning any Apple framework
- 17.8 · APNs tokens, payload budgets and notification triggers
- 17.9 · Cleaning location fixes, choosing geofences, and map geometry
- 17.10 · Contacts, EventKit, HealthKit units and sensor availability
- 17.11 · Records, system fields and CKError handling
- 17.12 · Passkey assertions, Apple ID tokens and Live Activity payloads