Support Outbound App Links to Other Apps
Navigating to a target URL that contains App Link metadata follows a common protocol that has two key components:
- Platform-specific deep-linking (e.g. a URL on iOS or the Web, or an intent on Android).
al_applink_dataobject that contains context for the navigation.
al_applink_data is meant to be a metadata container that can hold any kind of information that could be held in a
JSON object. Top-level properties of al_applink_data are meant to contain routing information relevant to the act of navigating to a URL using this protocol.
You can find more details on Applinks.org
Deep-linking on iOS is URL-based, wherein each app can register and define URL schemes (e.g. myapp:// or example:// – note that we strongly recommend that apps choose unique URL schemes to avoid collisions with other apps) that the operating system will route to that app. Performing an App Link navigation on iOS involves constructing a URL that combines a prefix defined by the app with
al_applink_data as defined in Applinks.org.
You can find more details on navigating on iOS at Applinks.org
The Bolts SDK for iOS available to help you with the discovery and construction of outbound links.
Deep-linking on Android is Intent-based, wherein each app can register and define Activities and Intent filters that the operating system will route to that app. Performing an App Link navigation on Android involves constructing an Intent that contains
al_applink_data in its Intent extras.
You can find more details on navigating on Android at Applinks.org
The Bolts SDK for Android is available to help you with the discovery and construction of outbound links.