When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You help plan, implement, and optimize App Clips — lightweight iOS experiences (max 15MB) that users can launch instantly without installing the full app.
App Clips are small, focused pieces of your app that users can use without downloading the full app. They appear in:
| Target | Limit |
|---|---|
| App Clip binary | 15MB max (thinned, downloaded on demand) |
| App itself | No change |
This forces you to ship only the essential experience.
| App Type | App Clip Experience |
|---|---|
| Parking/transit | Pay for parking or buy a ticket |
| Restaurant | View menu, order, or pay |
| Retail | Product preview or loyalty card |
| Fitness | Try a single workout |
| Games | Play a demo level |
| Finance | Calculator or quick quote |
| Events | Ticket purchase or check-in |
| Utilities | Use core feature once |
The key question: What is the minimum experience that demonstrates your app's core value?
App Clips appear in App Store search as a separate card below your full app result — labeled "App Clip" with an "Open" button (not "Get").
ASO implication: The App Clip card inherits your app's title and description metadata. Optimizing your main listing improves App Clip discoverability too.
Each App Clip is triggered by a URL:
https://yourdomain.com/clip/[experience]
Configure in App Store Connect → Your App → App Clip Experiences.
Always include a clear upgrade prompt:
// Show SKOverlay after the user gets value from the clip
let config = SKOverlay.AppClipConfiguration(position: .bottom)
let overlay = SKOverlay(configuration: config)
overlay.present(in: windowScene)
Show the overlay after the user has experienced value — not immediately.
You can configure multiple App Clip experiences (one per URL pattern):
| Experience | URL | Use Case |
|---|---|---|
| Default | yourdomain.com | General / App Store search |
| Location | yourdomain.com/location/123 | Maps, NFC at specific location |
| Campaign | yourdomain.com/promo/summer | Marketing campaign |
| Feature | yourdomain.com/feature/x | Specific feature demo |
Each experience can have its own:
The card is shown before the App Clip launches:
| Field | Limit | Tips |
|---|---|---|
| Title | 18 chars | Clear action: "Order Coffee" not "App Name" |
| Subtitle | 13 chars | Reinforce the value: "Skip the line" |
| Header image | 3000×2000px | Show the outcome, not the UI |
| Action button | — | Use context-specific text: "Order", "Pay", "Play" |
Track in App Store Connect → App Analytics → App Clips:
| App Clip | Full Install | |
|---|---|---|
| User friction | Very low | Higher |
| Commitment | Low | High |
| Retention | Low (one-time use) | High |
| Conversion from Clip | — | 3–5× higher than cold traffic |
| Best for | Discovery + conversion | Retention + monetization |
Setup:
- [ ] App Clip target added to Xcode project
- [ ] App Clip < 15MB (use size report in Xcode)
- [ ] Associated Domains entitlement configured
- [ ] App Clip experience URLs registered in App Store Connect
UX:
- [ ] Core value delivered within 60 seconds
- [ ] Sign in with Apple or Apple Pay (no custom sign-up)
- [ ] SKOverlay shown post-value (not immediately)
- [ ] Clear data handoff when user installs full app
App Store Connect:
- [ ] Default App Clip experience configured
- [ ] Header image uploaded (3000×2000px)
- [ ] Title ≤ 18 chars, subtitle ≤ 13 chars
- [ ] Additional experiences for locations/campaigns (if applicable)
aso-audit — Clip discoverability depends on main app ASOonboarding-optimization — Apply same "value-first" principles to Clip experienceua-campaign — Drive traffic to App Clip URLs in paid campaignsapp-store-featured — App Clips can support featuring eligibilityまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and configure Bluetooth and Wi-Fi accessories using AccessorySetupKit. Use when presenting a privacy-preserving accessory picker, defining discovery descriptors for BLE or Wi-Fi devices, handling accessory session events, migrating from CoreBluetooth permission-based scanning, or setting up accessories without requiring broad Bluetooth permissions.
日本語の概要は準備中です。原文の説明を表示しています。
Implement, review, or improve Live Activities and Dynamic Island experiences in iOS apps using ActivityKit. Use when building real-time updating widgets for the Lock Screen and Dynamic Island — delivery tracking, sports scores, ride-sharing status, workout timers, media playback, or any time-sensitive information that updates in real time. Also use when working with ActivityKit, ActivityAttributes, Activity lifecycle (request/update/end), Dynamic Island layouts (compact/minimal/expanded), push-to-update Live Activities, or Lock Screen live widgets.
日本語の概要は準備中です。原文の説明を表示しています。
Measure ad effectiveness with privacy-preserving attribution using AdAttributionKit. Use when registering ad impressions, handling attribution postbacks, updating conversion values, implementing re-engagement attribution, configuring publisher or advertiser apps, or replacing SKAdNetwork with AdAttributionKit for ad measurement.
日本語の概要は準備中です。原文の説明を表示しています。
Implement AlarmKit alarms and countdown timers for iOS and iPadOS with Lock Screen, Dynamic Island, and Apple Watch system UI. Covers AlarmManager scheduling, AlarmAttributes and AlarmPresentation, AlarmButton stop and snooze actions, authorization, state observation, and Live Activity integration. Use when building wake-up alarms, countdown timers, or alarm-style alerts that need Apple's system alarm experience.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
日本語の概要は準備中です。原文の説明を表示しています。