Skip to main content
ClaudeWave
Skill1.5k repo starsupdated 1mo ago

app-clips

App Clips is a skill for planning and implementing lightweight iOS experiences up to 15MB that users can launch instantly without downloading the full app. Use this when optimizing app discovery through App Store search results, QR codes, App Clip codes, websites, Safari, Messages, Maps, and physical NFC/visual codes, or when strategizing minimum viable experiences for parking, restaurants, retail, fitness, gaming, finance, events, and utilities use cases.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/Eronred/aso-skills /tmp/app-clips && cp -r /tmp/app-clips/skills/app-clips ~/.claude/skills/app-clips
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# App Clips

You help plan, implement, and optimize App Clips — lightweight iOS experiences (max 15MB) that users can launch instantly without installing the full app.

## What App Clips Are

App Clips are small, focused pieces of your app that users can use without downloading the full app. They appear in:

- **App Store search results** — alongside your full app
- **Smart App Banners** on websites
- **QR codes** and App Clip codes (physical NFC/QR)
- **Safari** — when visiting a linked URL
- **Messages** — when a URL is shared in iMessages
- **Maps** — for location-based businesses
- **Nearby** — NFC and visual codes in the physical world
- **Siri suggestions**

## Size Limit

| Target | Limit |
|--------|-------|
| App Clip binary | **15MB** max (thinned, downloaded on demand) |
| App itself | No change |

This forces you to ship only the essential experience.

## Best Use Cases

| 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 Clip Discovery in the App Store

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").

- Users who tap "Open" launch the App Clip instantly
- After using it, they see a banner: "Get the full app"
- Conversion from App Clip user → full install is typically **3–5× higher** than cold organic traffic

**ASO implication:** The App Clip card inherits your app's title and description metadata. Optimizing your main listing improves App Clip discoverability too.

## Technical Requirements

### What to include in the App Clip

- Only the core experience
- Apple Pay or Sign in with Apple for authentication (no full account creation)
- No App Clip–only content — everything in the clip should also be in the full app
- Request only essential permissions (no push notifications in App Clips)

### URL scheme

Each App Clip is triggered by a URL:
```
https://yourdomain.com/clip/[experience]
```

Configure in App Store Connect → Your App → App Clip Experiences.

### Handoff to Full App

Always include a clear upgrade prompt:

```swift
// 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.

## App Clip Experiences

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:
- Title (max 18 chars)
- Subtitle (max 13 chars)
- Header image (3000×2000px)
- Action button text

## App Clip Card Design

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" |

## Measurement

Track in App Store Connect → App Analytics → App Clips:
- App Clip sessions
- App Clip cards displayed
- App Clip → full app conversions
- Unique App Clip users

## App Clip vs Full App Install Trade-offs

| | 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 |

## Implementation Checklist

```
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)
```

## Related Skills

- `aso-audit` — Clip discoverability depends on main app ASO
- `onboarding-optimization` — Apply same "value-first" principles to Clip experience
- `ua-campaign` — Drive traffic to App Clip URLs in paid campaigns
- `app-store-featured` — App Clips can support featuring eligibility
ab-test-store-listingSkill

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.

android-asoSkill

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.

app-analyticsSkill

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

app-icon-optimizationSkill

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

app-launchSkill

When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.

app-marketing-contextSkill

When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

app-preview-videoSkill

When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).

app-rejection-recoverySkill

When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.