The Problem They Solve
Users often encounter situations where they need an app's functionality briefly: paying for parking, renting a scooter, ordering food at a restaurant, or checking in at a venue. Installing a full app for a one-time use creates friction that many users will not tolerate.
App Clips (iOS) and Instant Apps (Android) solve this by letting users access a focused piece of your app instantly, without going through the install process.
iOS App Clips
What Is an App Clip?
An App Clip is a lightweight portion of your iOS app that is discoverable at the moment it is needed. It loads in seconds, provides focused functionality, and offers a path to install the full app.
Constraints
- Size limit: 15 MB (after app thinning). This is strict and enforced.
- Temporary: App Clips are automatically removed after a period of inactivity (30 days).
- Limited APIs: No access to HealthKit, CallKit, or contacts. Cannot perform background activity (with few exceptions).
- Storage: Data is deleted when the App Clip is removed. Use the App Clip's keychain or shared data with the full app (via App Groups) to preserve data if the user installs.
Discovery Methods
Users encounter App Clips through:
- NFC tags: Tap a physical tag to launch the App Clip
- QR codes / App Clip Codes: Scan a visual code (Apple's own App Clip Code format or standard QR)
- Safari App Banners: Smart banners on websites
- Messages: Shared links that expand into App Clip cards
- Maps: Business listings with App Clip integration
- Location-based suggestions: Siri suggestions near relevant locations
Building an App Clip
An App Clip is a separate target in your Xcode project:
- Create an App Clip target alongside your full app target
- Share code between targets using shared frameworks or modules
- The App Clip uses the same SwiftUI/UIKit code, just a smaller subset
- Associate your App Clip with a URL through the AASA file (same as Universal Links)
- Configure the App Clip experience in App Store Connect (invocation URL, header image, action button text)
App Clip Card
When an App Clip is invoked, the system shows a card with:
- App icon and name
- A description of the action
- An "Open" button
- The source (NFC, QR, Safari, etc.)
This card provides transparency to the user about what they are launching.
Android Instant Apps
What Is an Instant App?
An Instant App (now called Google Play Instant) lets Android users run your app without installation. The user taps a URL, and the relevant module of your app loads from Google Play.
How It Works
Instant Apps are built using Android App Bundles with feature modules:
- Split your app into a base module and feature modules
- Each feature module can be loaded on demand
- The instant-enabled module must be under 15 MB (total loaded size)
- Users access instant experiences through URLs, Google Play "Try Now" buttons, or deep links
Constraints
- Size limit: 15 MB for the instant experience
- Limited access to some APIs (background services, device identifiers)
- Must use HTTPS URLs
- Requires target API level 26+
- Must be published through Google Play
Building an Instant App
- Enable "Google Play Instant" in your module's manifest
- Split functionality into feature modules using dynamic delivery
- Associate your app with a website URL (Digital Asset Links)
- Handle the URL intent to show the correct feature
- Upload to Google Play and enable the "Try Now" button
Design Principles
Both platforms share common design principles for lightweight experiences:
Focus on One Task
Do not try to squeeze your entire app into a Clip or Instant App. Pick the single most valuable action:
- A parking meter app: Enter spot number and pay
- A restaurant: View menu and place order
- A rental service: Scan QR and start rental
Fast and Lightweight
Every millisecond counts. Users expect instant loading:
- Minimize network requests
- Optimize images aggressively
- Pre-compile and cache where possible
- Use skeleton screens during loading
Path to Full Install
Always provide a clear, non-intrusive way to install the full app:
- Show an install prompt after the user completes their task
- Transfer their data seamlessly if they install
- Do not block the primary flow with install prompts
Comparison
| Feature | App Clips (iOS) | Instant Apps (Android) |
|---|---|---|
| Size limit | 15 MB | 15 MB |
| Framework | SwiftUI / UIKit | Jetpack Compose / Views |
| Discovery | NFC, QR, Safari, Maps, Messages | URLs, Play Store, deep links |
| Auth | Sign in with Apple only (initially) | Full auth options |
| Payments | Apple Pay required | Google Pay supported |
| Retention | Removed after 30 days inactive | Not installed by default |
Practical Considerations
In 2026, adoption of App Clips and Instant Apps remains moderate. Many businesses find that a well-optimized mobile website serves the same purpose for casual users. The strongest use cases are physical-world interactions (NFC payments, venue check-ins, equipment rentals) where the native experience provides meaningful advantages over a web page.