Mobile deep linking
In the context of mobile apps, deep linking consists of using a uniform resource identifier (URI) that links to a specific location within a mobile app rather than simply launching the app. Deferred Deep Linking allows users to deep link to content even if the app isn't already installed. 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 allow for deep linking by default, enabling deep linking on mobile apps requires these apps be configured to properly handle a uniform resource identifier (URI). Just like a URL is an address for a website, a URI is the address for an app on a mobile device. Examples of URIs that launch a mobile app:
twitter://is the iOS URI to launch Twitter’s mobile app
YouTube://is the iOS URI to launch YouTube’s mobile app
The format of the URI used to trigger or deep link an app is often different depending on the mobile operating system. Android devices work through intents, BlackBerry 10 devices works through BB10's invocation framework, Firefox OS devices works through Web Activities, iOS devices works through the openUrl application method, and Windows Phone 8 devices works through the UriMapper class.
fb://profile/33138223345is an example of a mobile deep link. The URI contains all the information needed to launch directly into a particular location within an app, in this case the profile with id '33138223345', i.e., the Wikipedia page, within the Facebook app, instead of simply launching the Facebook app
- eBay's apps demonstrate the use of different schemes by platform.
eBay://launch?itm=360703170135is the URI that deep links into eBay’s iOS app while
eBay://item/view?id=360703170135links into eBay’s Android app
The greatest benefit of mobile deep linking is the ability for marketers and app developers to bring users directly into the specific location within their app with a dedicated link. Just as deep links made the web more usable, mobile deep links do the same for mobile apps.
Unlike deep links on the web, where the link format is standardized based on HTTP guidelines, mobile deep links do not follow a consistent format. This causes a confusing user experience because different sets of links are required to access the same app on a different mobile operating system.
Google allows app developers, who have both iOS and Android apps, to surface in-app content via mobile Google searches. Developers will need to submit their app and deep linking apps on both iOS and Android to be indexed by Google. Alternatively, developers can use Google's short links to deep link mobile app users if the app is installed and direct others to the webpage.
One example of a better user experience made possible because of deep link and data passing through 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. For example, to search for hotels in Boston, a user currently needs to:
- Perform a Google search for a term
- See that a company has relevant content in its app
- Manually switch from the browser to the app (download the app first if required)
- Perform the search again in the app
That can be shortened to:
- Search on Google
- Select the in-app search result to view in-app (if app is installed)
- "Android Intents Filters".
- "BlackBerry 10 Invocation Framework".
- "FireFox OS Web Activities".
- "iOS openURL Application Method".
- "Windows Phone UriMapper".
- Nielsen, Michelle (Mar 3, 2002). "Deep Linking is Good Linking". Nielsen Norman Group. Retrieved Aug 14, 2013.
- Kokalitcheva, Kia (Jan 7, 2015). "Yozio lets app makers spot where new users are coming from and personalize the download experience". VentureBeat.