#510: shortcuts member of Web App Manifest

Visit on Github.

Opened Apr 27, 2020

Hello TAG!

I'm requesting a TAG review of shortcuts member of Web App Manifest.

A number of operating systems offer a means by which authors add menu items to the app launcher icon itself. These provide quick access to key tasks for an app. Typically, these are exposed via a right click, long tap, or a similar context menu-triggering action. The list of shortcut actions often contains a mixture of static and dynamic shortcuts. Generally these number around 4–5, depending on the platform—or in the case of Android, the launcher—used. Adding these to the web platform provides an equivalent capability to native apps on many platforms.

Further details:

  • I have reviewed the TAG's API Design Principles
  • The group where the work on this specification is currently being done: Web Applications Working Group
  • Major unresolved issues with or opposition to this specification: N/A
  • This work is being funded by: Microsoft, Intel, Google

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback

Discussions

Discussed Apr 27, 2020 (See Github)

Kenneth: already gave a lot of feedback

Dan: I should be on it too.

Comment by @kenchris Apr 27, 2020 (See Github)

I will let some of my co-TAG members review this as I have been involved - but I will just say that I am happy how it turned out and I think we have been good in incorporating all the different feedback from different stakeholders, and I am happy to see this move forward

Discussed May 11, 2020 (See Github)

Ken: like "shorcuts" on android... limit how many you can have... you add on install time...

Dan: what's the mozilla standards position? Multi-engine support?

Comment by @cynthia May 12, 2020 (See Github)

Couldn't see anything substantial during the review.

Comment by @torgo May 12, 2020 (See Github)

We are reviewing in a TAG breakout and we are happy with this. However, is there a standards position on this from Mozilla or any other cross-engine support info you can provide @jungkees ?

Comment by @aarongustafson May 13, 2020 (See Github)

However, is there a standards position on this from Mozilla or any other cross-engine support info you can provide?

I am not aware of anything formal, though our informal discussions with @hober and @marcoscaceres at TPAC last year were quite positive. The PR into the Manifest spec includes references to the bugs we filed for each engine.

Comment by @kenchris May 13, 2020 (See Github)

@dbaron will file a standards position issue with Mozilla for completeness sake.

Apart from that, the TAG is happy with this feature!

Comment by @jungkees May 13, 2020 (See Github)

Thank you TAG for the review!