Mobile deep linking: Difference between revisions
m →Complexity of mobile deep linking and the need for a streamlined solution: WP:CHECKWIKI error fixes using AWB (10269) |
Available standards and tools |
||
| Line 27: | Line 27: | ||
Another solution proposed by [[URX (company)|URX]] requires prepending any normal web link with urx.io/ to convert it into a deep link.<ref name=wallstreetjournal>{{cite news |url=http://blogs.wsj.com/digits/2014/04/28/urx-raises-12-million-sets-sights-on-links-inside-apps/ |title=URX raises 12 million sets sights on links inside mobile apps|author=Winkler, Rolfe |publisher=''The Wall Street Journal'' |date=April 28, 2014}}</ref> Omnilinks work across all devices and will route users into a specific page in an app if that user has the app installed.<ref name="wallstreetjournal"/> |
Another solution proposed by [[URX (company)|URX]] requires prepending any normal web link with urx.io/ to convert it into a deep link.<ref name=wallstreetjournal>{{cite news |url=http://blogs.wsj.com/digits/2014/04/28/urx-raises-12-million-sets-sights-on-links-inside-apps/ |title=URX raises 12 million sets sights on links inside mobile apps|author=Winkler, Rolfe |publisher=''The Wall Street Journal'' |date=April 28, 2014}}</ref> Omnilinks work across all devices and will route users into a specific page in an app if that user has the app installed.<ref name="wallstreetjournal"/> |
||
== Available standards and tools == |
|||
=== Standards === |
|||
* [http://appurl.org/ AppURL] from Quixey |
|||
* [http://applinks.org/ App Links] from Facebook |
|||
* [https://developers.google.com/app-indexing/ App Indexing] from Google |
|||
* [https://dev.twitter.com/docs/cards/types/app-card App Cards] from Twitter |
|||
=== Non-standards === |
|||
* MobileDeepLinking.org |
|||
* Deeplink.me |
|||
=== Tools === |
|||
* URX |
|||
== References == |
== References == |
||
Revision as of 11:59, 3 July 2014
In the context of the mobile apps, deep linking consists of using an uniform resource identifier (URI) that links to a specific location within a mobile app (i.e. exampleApp://location/123456), rather than simply launching the app (i.e. exampleApp://). Depending on the mobile device, the URI required to trigger the app may be different (e.g. exampleiOSApp://location/123456 versus exampleAndroidApp://launch?location=123456).
Example
This link fb://profile/33138223345 is 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 Wikipedia page within the Facebook app, instead of simply launching the Facebook app fb://.
Deep linking and mobile operating systems
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).[1][2] 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 works through intents,[3] BlackBerry 10 devices works through BB10's invocation framework,[4] Firefox OS devices works through Web Activities,[5] iOS devices works through the openUrl application method,[6] and Windows Phone 8 devices works through the UriMapper class.[7] Examples of URIs that deep link directly into a mobile app:
- eBay://launch?itm=360703170135 is the URI that deep links into eBay’s iOS mobile app
- eBay://item/view?id=360703170135 is the URI that deep links into eBay’s Android mobile app
Complexity of mobile deep linking and the need for a streamlined solution
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,[8] 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.
Several organizations have developed solutions to help simplify this confusing user experience. One such solution is the creation of a smarter deep link that triggers the most appropriate response depending on the device accessed by the user.[9]
Another solution proposed by URX requires prepending any normal web link with urx.io/ to convert it into a deep link.[10] Omnilinks work across all devices and will route users into a specific page in an app if that user has the app installed.[10]
Available standards and tools
Standards
- AppURL from Quixey
- App Links from Facebook
- App Indexing from Google
- App Cards from Twitter
Non-standards
- MobileDeepLinking.org
- Deeplink.me
Tools
- URX
References
- ^ "URIs and Your Mobile App".
- ^ "AppURL Docs".
- ^ "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.
- ^ "Patent US8433800: Smart link system and method".
- ^ a b Winkler, Rolfe (April 28, 2014). "URX raises 12 million sets sights on links inside mobile apps". The Wall Street Journal.
{{cite news}}: Italic or bold markup not allowed in:|publisher=(help)