[w3ctag/design-reviews] `handle_links` manifest field ✨ (Issue #695)

Hola TAG!

I’m requesting an *early* TAG review of web app link handling. 

When clicking on a link, the default behavior is that the browser will open and navigate to the specified URL. However, if a compatible application is installed, a user might prefer to have that application launch and "open" said link. This is the case for native apps that range from media consumption to productivity, where if installed, will open when clicking on a link with related content. This is generally the preferred way to interact with the referenced content. To achieve this, an installed application might want to register itself to handle links and create this seamless flow. From a UX perspective, it is desirable to give users choice on how they prefer the link to be opened, and it is important since it creates the cohesive and integrated experience mentioned previously.

- Explainer: https://github.com/WICG/pwa-url-handler/blob/main/handle_links/explainer.md

- Security and Privacy self-review: https://raw.githubusercontent.com/WICG/pwa-url-handler/main/handle_links/Security%20and%20Privacy%20Self-Review%20Questionnaire.md

- Primary contacts: 
  - Diego Gonzalez (@diekus), Microsoft
  - Lu Huang (@luhuangmsft), Microsoft
  - Mandy Chen (@mandymsft), Microsoft
- Organization/project driving the design: Microsoft
- External status/issue trackers for this feature (publicly visible, e.g. Chrome Status): https://chromestatus.com/features/5740751225880576


Further details:
- [ x ] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
- The group where the incubation/design work on this is being done (or is intended to be done in the future): WICG
- The group where standardization of this work is intended to be done ("unknown" if not known): unknown
- Existing major pieces of multi-stakeholder review or discussion of this design: 
- Major unresolved issues with or opposition to this design: N/A
- This work is being funded by: Microsoft

You should also know that this work is the evolution of the URL Handling feature. We have iterated on the idea of how URL handling should work on installed web apps, creating a clearer separation of roles between `handle_links` and `scope_extensions `. 

The explainer to the previous “shape” of this feature is listed here: https://github.com/WICG/pwa-url-handler/blob/main/explainer.md. 

The TAG review for the previous “shape” of this feature is: https://github.com/w3ctag/design-reviews/issues/552 .

Related APIs: `scope_extensions`: https://github.com/WICG/manifest-incubations/blob/gh-pages/scope_extensions-explainer.md


We'd prefer the TAG provide feedback as:
💬 leave review feedback as a comment in this issue and @-notify : @diekus, @luhuang

✨

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/695