Re: [manifest] Deep linking - need proper use cases and requirements analysis (#363)

I know native deep linking well. Will spend some time looming into a reply
for this thread (sorry for this  empty reply)

On Mon, 17 Aug 2015 09:50 Kenneth Rohde Christiansen <
notifications@github.com> wrote:

> I haven't unfortunately. @PaulKinlan <https://github.com/PaulKinlan>, do
> you have anyone on your team familiar with the native deep linking who
> could look at this?
>
> @alxlu <https://github.com/alxlu> as long as it is restricted to URL
> scopes within its own domain, I think this could work. The problem is when
> multiple apps register for the same scopes, but maybe that can be looked at
> as an enhancement in the future.
>
> I would assume that registering for these scopes (and adding handlers)
> should happen in a Service Worker, as the app might not be running and
> because it gives a lot of flexibility.
>
> We could then look at how to make the Service Worker launch the app in
> "web app state" - using the info from the manifest.
>
> It is already possible to launch the app from the Service Worker based
> push notifications, but I would assume that that also just launches the app
> in the browser currently. @PaulKinlan <https://github.com/PaulKinlan> can
> you confirm? We should really fix this.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/manifest/issues/363#issuecomment-131734446>.
>


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/363#issuecomment-131736227