What is an App Clip?

The problem it addresses

Installing an app is a large commitment for a small task. Paying for parking, ordering at a table, renting a scooter, checking in — each is a one-minute interaction that traditionally required a download, an account and a permission prompt first.

An App Clip removes that. The user taps an NFC tag, scans a code or follows a link, and a small portion of the app runs immediately with no install.

Where it fits

• Physical-world tasks triggered by a tag or code at the point of need.
• One-off transactions where a full install would never be justified.
• Trial before install, letting someone experience the product before committing.
• Not general app distribution — the size limit and scope constraints are real.

Why adoption has been narrow

App Clips work well and are used less than their design merits, for a straightforward reason: they require the physical or contextual trigger to already be in place.

The compelling use cases involve a tag on a parking meter, a code on a table, a link at a venue — all of which require deployment in the physical world by someone with a commercial reason to do it. Where that infrastructure does not exist, the App Clip has no entry point.

The instructive parallel is Instant Apps on Android, which addressed the same problem and saw similarly limited adoption for similar reasons. Both are good answers to a question most businesses were not asking.