App Clips remain today the most credible option for getting a mobile app feature used without installation, especially on iPhone. On the Android side, Google Play Instant Apps are nearing the end of the road: Google has announced they will be discontinued starting in December 2025. For an SMB project, the issue is therefore no longer “iOS or Android without installation,” but rather “which short journey really deserves an App Clip?”
App Clips: what this really changes for a mobile project
An App Clip is a small morceau of an iOS app launched without downloading the full application. Apple introduced it with iOS 14 lors at WWDC 2020, with a simple idea: enable a quick action, such as paying, booking, renting, ordering, or unlocking a service, without friction at the start.
For a business owner, the benefit is concrete. You can test a very targeted use case without asking the user to immediately agree to install an app, create a full account, and give up several minutes of attention. This is especially relevant when the need is immediate: restaurant table, borne, storefront, event, coupon, parking, local service.
The limitation is just as concrete. An App Clip is not a mini marketing app that you tack on at the end of a project. It must be designed as a porte entry point to a measurable action. If the journey is not faster than a good mobile site, the investment is hard to justify.
Android Instant Apps: why the comparison has changed
Google introduced Android Instant Apps at Google I/O in May 2016, then opened the technology to all developers in May 2017. At the time, the ambition looked very much like Apple’s: let users try a native Android experience without installation, from Google Play or a compatible link.
The context has shifted. The Android Developers documentation indicates that Google Play Instant will no longer be available starting in December 2025: Instant Apps will no longer be publishable via Google Play, the Instant APIs of Google Play services will stop working, and users will no longer be served these experiences through Play. Google cites developer feedback and continued investment in the ecosystem as justification.
In other words, for a new project launched in France in 2026, building a strategy around Google Play Instant would be a bad bet. There may still be Android topics related to deep links (that is, links that open a page or feature directly in the app), Progressive Web Apps, or a standard application, but not a roadmap centered on Instant Apps.
If you are comparing mobile approaches before choosing an architecture, this guide on technical fundamentals of a mobile app helps lay the groundwork: native, hybrid, web app, API, security, and maintenance.
Where an App Clip apporte real value
The best use case is a moment when the user has a clear intention, but little patience. They are standing in front of a product, a poster, a checkout, a table, or a pickup point. They want to act now. Not “discover your world.” Just complete a task.
Apple documents several launch methods in 2026: App Clip Code, NFC tag (contactless chip), QR code, Safari, Messages, Maps, location-based suggestions, and other applications. Since January 2021, Apple’s App Clip Codes can combine a scannable visual marker and, in some cases, an integrated NFC chip. Apple also recommends these NFC codes when the user can physically access the support: restaurant table, point of sale, storefront, signage, gift card, coupon, or offer.
In the projects we carry out, we often see the same mistake: trying to put too much into the short experience. An effective App Clip chooses one action, not five. Order a menu. Validate a ticket. Book a time slot. Claim a discount. If you add the full catalog, historique, preferences, referrals, and customer account, you are recreating an app under a tighter constraint.
Physical campaigns can also be concerned. A standard QR code on a poster often leads to a web page. An App Clip can go further when the action requires native iOS capabilities, such as Apple Pay, precise geolocation, or smoother interaction. For field activations, some ideas align with the logic of connected street marketing, provided that you measure scan rate, action rate, and cost per conversion.
Costs, timelines, and technical constraints to plan for
An App Clip requires an associated full iOS application. This point often comes as a surprise. You are not publishing only an isolated experience: you are preparing a lightweight morceau connected to a main app, with its screens, permissions, server-side services, and configuration in App Store Connect.
Size limits have evolved. The App Store Connect documentation consulted in 2026 indicates maximum variant sizes of: 10 MB before iOS 16, 15 MB for iOS 16 and later, and up to 100 MB for certain invocation flows using only numerical codes on iOS 17 and later, subject to the conditions specified by Apple. Scanning App Clip Codes requires iOS 14.3 or later.
| Option | 2026 availability | Published limit or constraint | Estimated budget France | Typical timeframe |
|---|---|---|---|---|
| iOS App Clip | Available, documented by Apple | 10 MB, 15 MB, or up to 100 MB depending on iOS and invocation type | €8,000 to €25,000 if the app already exists; more if everything has to be created | 4 to 10 weeks |
| Google Play Instant | Discontinuation announced starting December 2025 | Android 5.0/API 21+, less than 15 MB before discontinuation | To be avoided for a new project | Not recommended |
| Mobile site / PWA | Available on iOS and Android | Depends on the browser, more limited hardware access | €5,000 to €20,000 depending on scope | 3 to 8 weeks |
| Full native application | Available on iOS and Android | Installation required, stores validation | €25,000 to €120,000 and more depending on the profession | 3 to 6 months |
These amounts are ballpark figures for the French market, varying depending on the existing setup, the level of design, the APIs to connect, GDPR compliance, and the necessary testing. At this budget level, it is better to fund an App Clip only if the short experience has a measurable business impact. Otherwise, a good fast mobile page can bring in more.
The less visible trap concerns the back office. The experience may seem small on the user side, but it often depends on a payment system, inventory, a CRM, a booking tool, authentication, or a server. If these building blocks are slow or poorly documented, the real cost is not in the iPhone screen, it is in the integration.
When the no-install app is a bad idea
The first bad case is a project that is too editororial. If your goal is to present your company, publish content, generate quote requests, or capture SEO traffic, an App Clip is not suitable. Google indexes the web, not your iOS micro-journey like a standard page. A performing website often remains the right foundation.
Another tricky case: recurring uses. If your customers come back every week to manage an account, track orders, receive notifications, or view a historory, installing a full application may be more consistent. The App Clip can serve as a first step, but not permanently replace the app.
Honestly, this technology is only justified if the moment of use is very short, very contextualized, and very profitable to streamline. A retail chain that wants to reduce the checkout line may find value in it. A B2B SME that sells long-term services with a three-month sales cycle, much less so.
For Android, the announced end of Google Play Instant requires a different way of thinking. Android best practices remain useful for the full application, especially regarding compatibility, performance, and Play Store publishing; this point is detailed in this guide on Android application development.
How to decide without choosing the wrong project
The right decision starts with a scenario, not a technology. Describe a real situation: where the user is, with what need, in how many seconds they must succeed, and which action is worth money for you. If that sentence remains vague, the project is too.
- Identify a single action: pay, book, scan, activate, pick up, try.
- Check that this action truly benefits from being native iOS rather than web-based.
- Estimate the volume: number of scans, equipped locations, expected conversion rate.
- Audit the systems to connect: payment, inventory, customer account, GDPR, analytics.
- Plan a simple measurement: launch, abandonment, completed action, possible installation.
On the agency side, the reflex is to prototype the journey in low fidelity before coding. Three well-tested screens are better than a thirty-page specification. You quickly discover whether the user understands the entry point, accepts the scan, and completes the action without help.
The choice of technology comes next. Swift and SwiftUI are natural for the current iOS ecosystem, while a hybrid architecture may be relevant for the main application depending on the context. Approaches like Cordova still exist in some application portfolios; to understand their trade-offs, you can read this analysis of the hybrid mobile applications with Cordova.
One governance point remains: who maintains the experience after it goes live? iOS versions, App Store Connect rules, certificates, payment SDKs, and GDPR obligations change. An experience without installation is not an experience without maintenance.
Defining this type of project upfront helps avoid most unpleasant surprises: wrong target, wrong channel, underestimated integration, missing measurement. This is often where an outside perspective saves time, especially when the goal is to compare mobile site, full application, and App Clip with clear judgment.
FAQ about App Clips and Instant Apps
Does an App Clip work without the full app?
No. An App Clip is associated with a full iOS application that is published or intended to be published. It serves as a lightweight experience, but it relies on the main application project.
Do Android Instant Apps still exist in 2026?
Google announces that Google Play Instant will no longer be available as of December 2025. For a new project, it is better to consider a standard Android app, a PWA, or a mobile web experience.
How much does an App Clip cost for an SMB?
If the iOS app already exists, expect often around €8,000 to €25,000 depending on the integration. If the entire application and server foundation still needs to be created, the budget can go well beyond that.
Can a QR code to a mobile site replace an App Clip?
Yes, in many cases. If the action does not require native iOS features and the site is fast, a QR code linking to a mobile page costs less and also covers Android.