App Clips

App Clips

Build lightweight, instantly available versions of an iOS app for focused in-the-moment experiences or demos.

Contents

• App Clip Target Setup
• Invocation and Experience Routing
• Size and Capability Decisions
• Data, Notifications, and Location
• Common Mistakes
• Review Checklist
• References

App Clip Target Setup

An App Clip is a separate target in the same Xcode project as your full app:

1. File → New → Target → App Clip — Xcode creates the App Clip target, adds the Embed App Clip build phase to the full app target, and wires the association entitlements.
2. The App Clip bundle ID must be prefixed by the full app's bundle ID: com.example.MyApp.Clip.
3. Verify raw entitlement keys when diagnosing archive, signing, or App Store Connect failures:
   • App Clip target: com.apple.developer.on-demand-install-capable
   • App Clip target parent app link: com.apple.developer.parent-application-identifiers
   • Full app target associated App Clip link: com.apple.developer.associated-appclip-app-identifiers

Use Swift packages or shared source files for code needed by both targets. Add App Clip-specific compile branches with the APPCLIP active compilation condition, and avoid linking full-app-only frameworks into the App Clip target.

Validation checkpoint: Archive both targets and inspect their archived entitlements. If signing or validation fails, correct the three raw key/target assignments above and rearchive until both pass.

Invocation and Experience Routing

Read references/routing-and-experiences.md [blocked] when implementing invocation URL routing, App Store Connect experiences, Local Experiences, Safari Smart App Banners, QR/NFC/App Clip Codes, AASA, or associated domains.

App Clips receive NSUserActivityTypeBrowsingWeb activities. Keep the invocation router shared with the full app because, after installation, the full app replaces the App Clip and receives future invocations.

• SwiftUI: use .onContinueUserActivity(NSUserActivityTypeBrowsingWeb).
• UIKit cold launch: inspect connectionOptions.userActivities in scene(_:willConnectTo:options:).
• UIKit continuation: handle the actual NSUserActivity in scene(_:continue:).
• scene(_:willContinueUserActivityWithType:) is only advance notice and does not provide the URL.

Configure the required default App Clip experience in App Store Connect. Use advanced experiences for Maps integration, location association, production App Clip Codes, per-location cards, and precise physical-place routing; demo App Clip Codes can use the short demo App Clip link.

For custom URLs, add appclips:example.com to Associated Domains on both the full app and App Clip targets, and host an AASA file with the App Clip app identifier. For Safari banners, use app-id, app-clip-bundle-id, and optional app-clip-display=card; do not rely on app-argument for App Clip launches.

Validation checkpoint: Exercise each URL with _XCAppClipURL and a Local Experience, fix routing/AASA/experience mismatches, and repeat until the App Clip and installed full app reach the same destination.

Size and Capability Decisions

Use Size, capabilities, and promotion [blocked] as the authoritative checklist for feasibility reviews, size tiers and measurement, Background Assets, CloudKit, Live Activities, unsupported features, and full-app promotion. Load it whenever any of those topics is in scope.

Keep product reviews at the boundary level: state the size basis, invocation and download fit, capability exclusions, and handoff destination. Add implementation APIs only when the user asks for implementation.

Data, Notifications, and Location

Read references/data-handoff-notifications-location.md [blocked] when implementing App Group/full-app migration, keychain or Sign in with Apple handoff, ephemeral notifications, notification relaunch routing, or physical location confirmation.

Treat App Group storage as non-secret handoff state, not a trust boundary. The reference owns the iOS 15.4+ one-way keychain rule, Sign in with Apple verification, ephemeral-notification permission and relaunch routing, and physical-location confirmation—including their required raw keys and targets.

Common Mistakes

Exceeding the applicable App Clip size limit

Choose and measure the applicable limit using Size Limits [blocked].

Designing a marketing-only or web-view-heavy App Clip

App Clips should let people complete a focused task or full demo without installing the app. Avoid marketing-only clips, ad-heavy flows, splash screens, launch-blocking downloads, repeated install prompts, and web-view-heavy experiences that would work better as a website.

Review Checklist

Do not ship until every applicable gate passes; fix failures and rerun the same gate.

• Target IDs, all three raw entitlement keys, and shared-code boundaries are correct.
• Invocation works for SwiftUI/UIKit cold launch and continuation, then hands off to the full app.
• Associated domains, AASA, App Store Connect experiences, and local invocation tests pass.
• Size, capability, UX, Live Activity, and promotion decisions pass the feasibility review [blocked].
• Data, credential, notification, and location flows pass the detailed handoff checks [blocked].

References

• Routing and experiences [blocked]
• Data handoff, notifications, and location [blocked]
• Size, capabilities, and promotion [blocked]
• App Clips framework
• Creating an App Clip with Xcode
• Configuring App Clip experiences
• Responding to invocations
• Choosing the right functionality
• Confirming a person's physical location
• Sharing data between App Clip and full app
• Enabling notifications in App Clips
• Supporting invocations from your website and the Messages app
• Offering Live Activities with your App Clip
• Recommending your app to App Clip users
• APActivationPayload
• SKOverlay.AppClipConfiguration
• NSUserActivityTypeBrowsingWeb
• Creating App Clip Codes
• Distributing your App Clip
• App Clips HIG