A customer is standing at your checkout counter, ready to pay, and your app wants a 40MB download first.
Most people won’t wait. They pay cash, walk away, or use a competitor’s app instead.
This blog covers what App Clips are in 2026, how they work, what brands like Panera Bread and ParkWhiz got out of them, what they cost to build, and where the risks are.
According to Statista the average App Store listing converts browsers into installers only around 31% of the time; App Clips exist to work around exactly that drop-off.
An App Clip is a small, task-specific piece of your iOS app that opens instantly, without a full install, so a user can pay, order, or book in seconds.
Apple introduced App Clips with iOS 14 in 2020, and the feature is still active and expanding under iOS 26; this isn’t a legacy or deprecated capability.
Unlike a full app, an App Clip contains only the code needed for one job, such as ordering food or paying for parking, and nothing else.
It also disappears from a user’s device automatically if they don’t reuse it within a set window, so it never clutters the home screen the way an abandoned full app does.
An App Clip loads a lightweight slice of your app’s code from a link, code, or tag, lets the user complete one task, then offers a one-tap path to install the full app.
There are two outcomes: the user finishes the task and leaves, or they tap “Get the full app,” and the App Clip is replaced by the real installation on their device.
Size limits have changed as iOS has matured, and most existing blogs on this topic still quote the original 2020 numbers.
| iOS Version | App Clip Size Limit | Notes |
|---|---|---|
| Before iOS 16 | 10MB | Apple’s original App Clip limit |
| iOS 16 and later | 15MB | Standard App Clip binary size |
| iOS 17 and later | Up to 100MB | Only for specific numeric-code-only invocation flows, per Apple’s current App Store Connect documentation |
A slow App Clip defeats the purpose, so Apple keeps the cap tight enough to force load times of a few seconds.
Google shut down Play Instant, Android’s equivalent to App Clips, in December 2025. App Clips is now the only mature no-install app experience left on a major mobile platform.
For years, agencies pitched a “lightweight app experience” as a cross-platform play: App Clips on iOS and Instant Apps on Android.
That comparison no longer holds. Google’s own developer documentation confirms Instant Apps can no longer be published, and the supporting Play services APIs have stopped working.
For businesses that also build an Android App pairing iOS App Clips with a mobile-optimized web fallback for Android is the realistic architecture, not a like-for-like native feature on both platforms.
Pick the right format for the job before you spend on any of them. Understanding mobile app development costs helps put the investment behind each approach into perspective.
| Option | Best For | Key Limitation | Estimated Cost |
|---|---|---|---|
| App Clip | iOS users needing one fast task: pay, order, book | iOS-only, 15–100MB cap, tied to a parent app | $8,000–$25,000 (add-on) |
| Full Native App | Ongoing engagement, loyalty, complex features | Requires install; higher acquisition friction | $40,000–$150,000+ |
| Progressive Web App | Cross-platform reach without App Store approval | No native discovery via Maps, NFC, or App Clip Codes | $15,000–$50,000 |
Users discover App Clips through seven main entry points, and each one fits a different physical or digital moment.
A user opens their iPhone camera and points it at a printed or on-screen QR code, and the App Clip launches directly without a separate scanner app.
This is the most common entry point because it works on signage, packaging, table tents, and receipts with no NFC hardware required.
Retailers use QR-triggered App Clips to let a shopper pull up product details or a checkout flow while standing in the aisle, cutting the gap between interest and purchase to a single scan.
When a user visits a website in Safari that has an associated App Clip, Apple shows a banner offering to launch the lightweight experience instead of the full site.
This only appears when the App Clip is actually supported on that device and task, so it never shows a broken or irrelevant option.
It’s a strong fit for businesses whose customers already land on the website first, since it converts existing web traffic into an app-quality experience without an install step.
An App Clip Code is Apple’s own visual design, combining a scannable pattern with optional NFC, and it’s built specifically to signal “an App Clip is available here.”
Unlike a generic QR code, it’s instantly recognizable to iPhone users as an Apple-native experience, which increases trust and scan rates in physical retail settings.
Businesses running pop-up stores or trade show booths use App Clip Codes on printed cards, since the code doubles as branding and as the launch mechanism.
An NFC tag encodes the same invocation URL as a QR code, but the user launches the App Clip with a single tap of their phone instead of a camera scan.
This matters in settings where scanning is awkward, such as a parking meter, a vending machine, or a table at a restaurant.
ParkWhiz uses NFC tags at parking spots specifically because a tap is faster than unlocking a phone, opening a camera, and framing a code while standing in traffic.
Apple Maps and Siri can surface an App Clip directly on a business’s location card, letting a user start an order or booking before they’ve even walked in the door.
Businesses need to register this integration with Apple; it doesn’t happen automatically just because an App Clip exists.
Panera Bread uses this specifically: searching for a nearby location in Apple Maps surfaces an “Order Food” button that opens their App Clip directly, without opening a browser or the App Store first.
iOS keeps a record of recently launched App Clips in the App Library, so a user who ordered from your App Clip last week can reopen it in one tap.
This matters because it gives App Clips a form of light-touch retention that a one-off web checkout page can’t offer.
For repeat-purchase businesses like coffee shops or gyms, this recent list functions like a lightweight loyalty shortcut without requiring a full app install.
A user can share an App Clip link through iMessage, and the recipient sees a rich preview that launches the App Clip directly, not a plain web link.
This turns word-of-mouth into a functional referral channel, since the person receiving the link can complete the same task the sender did, instantly.
A business running an event or referral promotion can rely on this to move users from a text message straight into a booking or signup flow with zero extra downloads.
The benefit isn’t the technology itself; it’s what happens to conversion when the install step disappears.
One industry analysis found a restaurant chain’s App Clip ordering flow saw more than double the conversion rate of its previous “install the app to order” flow, as reported by Mobiloud in 2026.
App Clips also cut acquisition costs, since a business isn’t paying for an App Store install just to get a single transaction completed.
Because App Clips share code with the parent app, engineering teams get a preview channel for new features without shipping a separate product.
App Clips can support a range of customer journeys, from quick purchases to one-time transactions, by removing the need for a full app download. Here are some of the most practical App Clip use cases across industries:
A shopper scans a QR code on a product display and gets full product details, reviews, and a direct purchase option inside the App Clip, without leaving the store aisle.
Nike uses this pattern at physical retail locations, pairing product discovery with loyalty program signup inside the same App Clip session.
This shortens the path from “I’m curious about this item” to “I bought it,” which matters most in stores with high foot traffic and low staff-to-customer ratios.
A diner scans a code at the table or finds “Order Food” on a Maps listing, and the App Clip handles the full menu, order, and Apple Pay checkout.
Panera Bread runs exactly this flow, letting a customer complete an order from Apple Maps search results without opening the App Store first.
For quick-service restaurants, this removes the single biggest friction point in mobile ordering: asking a first-time customer to install an app before they’ve even decided what to eat.
A driver taps an NFC tag at a parking meter or scans a code on a rental bike, and the App Clip handles payment in seconds without a prior signup.
ParkWhiz built its App Clip around this exact moment, since asking someone to download an app while blocking traffic is a lost customer.
Bike- and scooter-share operators use the same pattern, since a rider who has to install an app before unlocking a bike is a rider who walks to the next option instead.
An attendee scans a code at the entrance, and the App Clip pulls up their ticket, checks them in, and surfaces event details without a separate app.
Ticketmaster uses App Clips to speed up entry lines at venues, cutting the time between arrival and getting inside.
This use case works especially well for one-time or seasonal events, where asking attendees to install a full app for a single visit is a hard sell.
A customer taps a code at a branch, ATM, or partner location, and the App Clip handles a specific transaction, such as a quick balance check or a one-time payment.
This fits card issuers and neobanks that want to offer instant utility, like activating a new card, without requiring a full onboarding flow first.
Because App Clips can carry over data to the full app after install, a financial services company can convert a one-time task user into a fully onboarded account holder without repeating information collection.
App Clips only pay off if a business plans for the trade-offs up front, and most existing guides skip this entirely.
Maintenance overhead is real: an App Clip shares code with the parent app, but Apple still requires separate size checks, review, and testing for every release, adding QA work on top of the main app cycle.
Setting up an Advanced App Clip Experience in App Store Connect, associated domains, invocation URLs, and App Clip Code ordering has a real learning curve and can stall launches without prior experience.
Reach stays iOS-only. With Android’s Instant Apps gone, there’s no equivalent fallback for Android users beyond a standard mobile web page.
Analytics stay thin unless a user opts in to share diagnostics with the developer, which limits how precisely a business can measure App Clip performance compared to a full app.
Discoverability takes ongoing effort. App Clips don’t appear in App Store search, so visibility depends entirely on how well a business places QR codes, NFC tags, and links in the real world.
A basic App Clip, built on top of an existing iOS app, typically runs $8,000–$25,000, since most of the underlying logic and design system already exists.
Cost climbs when a business needs an Advanced App Clip Experience with multiple invocation methods, Maps integration, NFC hardware rollout, and custom App Clip Codes, each add scope.
Apple Pay integration, location services, and push notification permissions inside the App Clip also add development and testing time, since each one needs its own permission flow within the 15MB budget.
Build vs. buy: a business with an existing native iOS app should build an App Clip as an extension of that codebase; a business with no native app yet should evaluate developing an iOS app or whether a PWA fits the goal better before committing to an App Clip alone.
Apple continues to expand App Clip capacity under iOS 26, including the larger size allowance for numeric-code-only invocation flows introduced with iOS 17.
Google’s exit from Play Instant widens the platform gap through 2026, making App Clips a more distinct iOS-specific growth lever rather than one half of a cross-platform pair.
Developer forum activity around Apple Wallet and App Clip invocation flows in 2026 points to deeper integration between Wallet, Maps, and App Clips for payment-related use cases going forward.
Technource brings hands-on experience building native iOS products and lightweight mobile experiences designed around real customer journeys. Our team understands how App Clips fit into broader product ecosystems, from QR- and NFC-triggered interactions to fast checkout flows and seamless handoffs into full apps. This practical product-engineering approach helps businesses reduce friction at high-intent moments while keeping the App Clip aligned with their existing iOS architecture and long-term roadmap.
Our mobile team builds App Clips as an extension of your existing iOS codebase, not a bolt-on side project, which keeps maintenance overhead close to zero for your engineering team.
We scope Advanced App Clip experiences, Maps cards, NFC rollout, and App Clip Codes as part of the same engagement, so discovery and development aren’t handled by separate vendors.
We design the data handoff between App Clip and a full app up front, so a user who converts from a one-time task to a full install never has to re-enter information.
Our team of mobile app developers has shipped native iOS features across fintech, retail, and hospitality clients, which is exactly the cross-industry pattern App Clips depend on.
App Clips remain one of the fastest ways to turn a moment of intent into a completed transaction, and Apple hasn’t slowed investment in the feature going into 2026.
The size limits have loosened, the Android alternative is gone, and real businesses, from Panera to ParkWhiz to Ticketmaster, are already proving the model works.
The trade-off is upfront planning: get the invocation method, size budget, and analytics limitations right before you build, not after. Working with an experienced mobile app development company can help you account for these constraints before development begins. If you’re weighing whether an App Clip fits your app, talk to our mobile team before you scope the build.
An app clip is a small, task-specific part of an iOS app that opens instantly without a full install, letting a user pay, order, or book in seconds. App clips are capped at 15MB on iOS 16 and later, up from the original 10MB limit, with up to 100MB allowed for certain numeric-code-only invocation flows on iOS 17 and later. Yes. App clips remain an active, developing iOS feature under iOS 26, with expanded size limits and deeper Maps and Wallet integration. No. App clips are an iOS-only feature. Android’s equivalent, Google Play Instant, was shut down in December 2025, leaving no direct alternative. A basic app clip built on an existing iOS app typically costs $8,000–$25,000. Advanced App Clip Experiences with Maps, NFC, or custom codes cost more. Yes. App Clips support Apple Pay natively, which is why they’re widely used for parking payments, food ordering, and quick checkout flows. App clips remove themselves automatically after a period of inactivity. Users can also delete one manually from the App Library’s Recently Added section. Yes. App clips run under the same privacy and security rules as full apps, including permission prompts for location, camera, and notifications.