widgetkit

Use AppIntentConfiguration paired with an AppIntentTimelineProvider, which receives the user's configuration intent in its snapshot and timeline methods. Define a WidgetConfigurationIntent type available to the widget extension, then register the widget in a WidgetBundle annotated with @main.

TimelineProvider is for static, non-configurable widgets and uses completion handlers, while AppIntentTimelineProvider is for configurable widgets and uses async/await with the user's intent configuration. Prefer AppIntentTimelineProvider over the older SiriKit-based IntentTimelineProvider for new widgets.

Add the Push Notifications capability to the widget extension, implement a WidgetPushHandler, and register it with .pushHandler(...) on the widget configuration. Send APNs pushes with apns-push-type: widgets and a content-changed payload; the push triggers a timeline reload rather than delivering state.

The widget extension runs in a separate process, so you must enable App Groups on both targets and share data via UserDefaults(suiteName:) or the shared group container. After writing data, call WidgetCenter.shared.reloadTimelines(ofKind:) to refresh the widget.

Yes, Link can be used in .systemSmall, .accessoryRectangular, and larger system widgets, combined with one widgetURL(_:) as the general fallback. Never attach multiple widgetURL modifiers in the same view hierarchy, as behavior is undefined.

WidgetKit owns widget registration, controls, and surfaces, while Live Activity lifecycle, APNs content-state, and Dynamic Island depth belong to ActivityKit, and intent modeling, entities, Siri, and Shortcuts belong to App Intents. Keep only the integration points, such as ActivityConfiguration registration, in WidgetKit code.