App Clips are condensed versions of apps that enable users to access specific features without installing the entire application. Users can invoke app clips through Singular-powered QR codes, NFC tags, or links:
By integrating Singular's SDK or S2S API into your App Clips, Singular can attribute users that invoke your App Clip, as well as measure if they go on to install and use your main app later.
FAQ
- Follow Singular's iOS SDK Integration Guide to implement it in your App Clip target. Alternatively, integrate via Singular's S2S API to minimize the size of your App Clip. Discuss with your Singular representative if you'd like to leverage the Singular S2S API.
- In Xcode, under "Signing & Capabilities", make sure you use a shared App Group between your main app and App Clip:
- Contact Singular to update your app's AASA file with the Clip app
- SKAdNetwork measurement is not supported by iOS in App Clips
- Device IDs (IDFA, IDFV) are not available by iOS in App Clips.
- App Clips must adhere to size requirements and this includes any implemented SDKs. Singular's iOS SDK is 300kb
- App Clips targeting iOS 16 and later: The uncompressed App Clip binary can be up to 15 MB in size.
- App Clips targeting iOS 15 and earlier: the uncompressed App Clip binary can be up to 10 MB in size.
- App Clips targeting iOS 17 and later may have an uncompressed App Clip binary up to 50 MB if additional requirements are met
- App Clips require an internet connection on the device
Singular's iOS SDK adds just 300kB to the app. While the SDK footprint is minimal, due to App Clip size requirements we encourage exploring integrating via Singular's S2S API directly in the App Clip. Discuss with your Singular representative if you'd like to leverage the Singular S2S API.