17.6 · Live Activities, WeatherKit, App Clips and CarPlay
Some frameworks put your app outside the app: on the Lock Screen, in a car, on a card tapped at a shop. Each comes with hard constraints on time, size and entitlements that matter more than the API.
Mental model. These surfaces are constrained by design: tiny, short-lived and strictly reviewed. Know the limits before you design.
Beyond the app
Live Activities and WeatherKit.
- How do Live Activities (ActivityKit) and WeatherKit work, and what are their limits?
Live Activities show real-time, glanceable information (a delivery, a sports score, a ride) on the Lock Screen, in the Dynamic Island and in StandBy. You…
Instant and in-car
App Clips and CarPlay.
- What are App Clips and CarPlay, what constraints do they impose, and when would you build them?
An App Clip is a small, fast part of your app that users launch without installing it, from an NFC tag, QR code, App Clip Code, Maps place card, Safari banner…
More in System frameworks
- 17.1 · UserNotifications, APNs and how a push actually gets delivered
- 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.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