What problem does it solve?
It solves the problem of delivering lightweight iOS app entry points that open correctly via invocation URLs and physical codes, while keeping binaries small and handling the App Clip’s ephemeral lifecycle safely.
Core Features & Use Cases
- App Clip target setup & shared code: Configure a dedicated App Clip target, bundle identifiers, embed settings, and conditional compilation to share implementation with the full app.
- Invocation URL handling (NSUserActivity): Route web browsing invocations through
onContinueUserActivity and extract context from URLs to drive the correct UI state.
- Distribution, experiences, and QR/NFC/Messages: Set up default, demo, and advanced experiences with associated domains and AASA so that multiple entry points can map to the right App Clip behavior.
- Data migration to the full app: Persist critical user/session/order data via shared App Group storage (and optionally shared Keychain) so installing the full app continues seamlessly.
- Full-app promotion with SKOverlay: Recommend installing the full app after the user completes a task without interrupting them.
- Optional location confirmation: Verify physical presence using
APActivationPayload and NSAppClipRequestLocationConfirmation with lightweight constraints.
Quick Start
Use the app-clips skill to set up your App Clip target, register invocation handling with onContinueUserActivity, and configure an App Store Connect experience plus associated domains so QR/NFC and links open the correct in-clip context.