Best Practices

App Links enable you to provide your users an experienced optimized for their device when viewing content. You should optimize the display of links that have App Link metadata for your app. You may choose to take a user to the native app store when the app is not installed or display the name of the app based upon the App Link metadata for a given link.

As is common when navigating to links on the web, it’s useful to give users the ability to return to apps that they came from after navigating. On some platforms, such as Android and Windows Phone, there is a built-in notion of a back button that fulfills this function.

Some platforms such as iOS, however, lack a back button. As specified in the “Navigating on iOS” section, when one app navigates to another, it may provide a referer_app_link with enough information to allow the receiving app to provide a back button for its users. We recommend that the receiver of an App Link navigation display the standard “Touch to return” UI shown in the image below when an incoming navigation contains the referer_app_link metadata.

Bolts for iOS provides a reference implementation of this UI, which can be found in the BFAppLinkReturnToRefererController class. This implementation will handle showing and hiding the “Touch to return” UI at the appropriate times and will take care of performing the navigation back to the previous app to handle touches.