Depending on the mobile device platform, the URI required to trigger the app may be different.
Unlike the Web, where the underlying technology of HTTP and URLs allows for deep linking by default, enabling deep linking on mobile apps requires these apps be configured to properly handle a uniform resource identifier (URI).
[9] One example of a better user experience made possible because of the deep link and data passing through the install solution is one in which search information is passed into an app to bring the user to the exact information that drove them to the app.
Compared to a common web link, this implementation may reduce the number of steps required.
While there is currently no industry standard for deferred deep linking, various platform providers offer differing levels of support: