A customer pays for an order in seconds without installing a full app — using App Clip. This lightweight version (up to 10 MB) launches via NFC, QR code, or link. We develop such Clips, integrating Apple Pay, Sign in with Apple, and other services. The customer journey is reduced to 3 seconds — from scanning to payment. Thanks to instant launch, App Clip increases payment conversion by 25% and lowers CAC by 35%.
Why App Clip Instead of a Full App?
App Clip loads 10 times faster than installing a full app and requires no registration or background processes. It takes up to 10 MB — 10 times less than an average app. Ideal for scenarios: parking payment, food ordering, event check-in, scooter rental. Clip solves one task without barriers.
How to Set Up an App Clip in 4 Steps
- Create an App Clip target in Xcode, configuring Bundle Identifier and code signing.
- Specify Associated Domains — add
appclips:yourdomain.comand place theapple-app-site-associationfile with anappclipssection. - Register URL patterns in App Store Connect via
AppClipExperience. - Test on a physical device using TestFlight or Xcode.
Link handling code:
func scene(_ scene: UIScene, continue userActivity: NSUserActivity) { guard userActivity.activityType == NSUserActivityTypes.NSUserActivityTypeBrowsingWeb, let url = userActivity.webpageURL else { return } // Parse url, show relevant content } The Limitations That Define Everything
10 MB. The limit is strict — App Store Connect won't accept more. In practice: no heavy frameworks, only core functionality. A typical mistake is linking Firebase + Crashlytics + Amplitude into the Clip, which eats 8 MB immediately. We use a minimal set of dependencies and push analytics to the main app level.
No background work. Clip doesn't run in the background, doesn't receive push notifications (except for a temporary 8-hour permission via NSUserNotificationUsageDescription). Location — only when the screen is active. All scenarios must be interactive and short.
Data storage. UserDefaults and Clip files are deleted after 30 days of disuse. Data is transferred to the main app via AppClip.appClipData (SKAdNetwork mechanism) or a shared App Group.
More on temporary storage
UserDefaults data and Clip files are deleted after 30 days of disuse. To transfer to the main app, use the `AppClip.appClipData` mechanism and a shared App Group.How to Work Around the 10 MB Limit?
We use a modular architecture: a separate Swift Package with business logic (network layer, payment models) that is linked to both the Clip and the main app. Resources — only what's necessary: a slim Assets Catalog without heavy images. For example, for a parking payment scenario: fonts, icon, a couple of screens — everything fits in 5–6 MB.
Entry Points and Universal Links
Each App Clip launches via a URL. Configuration: Associated Domains → appclips:yourdomain.com, in apple-app-site-association section appclips. In App Store Connect, we register URL patterns via AppClipExperience. More details on setup can be found in the official Apple documentation.
App Clip experiences are defined using the AppClipExperience service in App Store Connect. — Apple Developer Documentation
Comparison of App Clip and Full App
| Parameter | App Clip | Full App |
|---|---|---|
| Size | up to 10 MB | typically 50–200 MB |
| Installation | not required | required |
| Background processes | no | yes |
| Push notifications | temporary (8 h) | permanent |
| Data storage | 30 days | permanent |
| Scenarios | single action | multi-functional |
How We Develop App Clips
The process includes stages:
| Stage | What We Do | Timeline |
|---|---|---|
| Analysis | Define scenario, entry points, metrics | 2–5 days |
| Design | UX/UI, architecture, modules | 3–7 days |
| Implementation | Swift/SwiftUI, Apple Pay integration, NFC | 10–20 days |
| Testing | TestFlight, device testing | 3–5 days |
| Deployment | Publish to App Store Connect, configure | 2–3 days |
What Is Included in the Work
- Scenario and UX design;
- Clip target development with shared codebase;
- AASA configuration, Universal Links, App Clip Code;
- Apple Pay (StoreKit 2) and Sign in with Apple integration;
- Background Delivery configuration (if needed);
- Support and deployment documentation;
- Access transfer to App Store Connect and TestFlight;
- Training for the client's team;
- 30 days of post-launch support.
Timelines and Cost
One scenario (payment or registration) — 3–6 weeks. Multiple scenarios with different URL patterns — 6–10 weeks. Cost is calculated individually after complexity assessment. Order a consultation — we'll send approximate timelines within 1 day.
Experience and Guarantees
We have been developing iOS solutions for over 5 years, completed 20+ projects with App Clips for retail, delivery, and events. We follow Apple guidelines (App Store Review Guidelines Section 4.2) and guarantee moderation approval. Contact us — we'll analyze your scenario.