W3C home > Mailing lists > Public > public-web-mobile@w3.org > January 2015

Re: Deep linking

From: Marcos Caceres <marcos@marcosc.com>
Date: Thu, 8 Jan 2015 13:07:40 +1000
To: public-web-mobile@w3.org, Dominique Hazael-Massieux <dom@w3.org>
Message-ID: <etPan.54adf4f4.7545e146.870@Marcos-MBP.local>



On January 6, 2015 at 8:46:15 PM, Dominique Hazael-Massieux (dom@w3.org) wrote:
> Hi,
>  
> In the past few months, several efforts have emerged to try to make
> native apps get some of the benefits of the Web (inter-linking), as well
> as to make them more integrated in the Web (seamless transition between
> browser-based and native-based views of the Web).

<snip>

> It's also an interesting twist to the usual “native vs Web” — it is
> closer to “native ♥ Web”, with benefits for all.

Web manifest defines a web app's "navigation scope" [1], which allows it to claim some portion of same-origin URL space as its own. An OS could use this URL space to route native apps navigations to these URLs to the appropriate (installed) web application. Native apps could then continue to use their own URLs (and fake protocols) to achieve the deep linking. 

so:

Facebook://whatever/

To "Awesome Web App": 
http://awesome.app/something/awesome

And back to, say, github (as works today):
github://somerepo_or_whatever 


[1] http://w3c.github.io/manifest/#navigation-scope
Received on Thursday, 8 January 2015 03:10:07 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 8 January 2015 03:10:08 UTC