Re: [w3c/manifest] App shortcuts / actions (#582)

I work on the team that maintains "jump lists" on Windows. Microsoft used the "msapplication-task" meta tag in the Windows 7 days:
https://technet.microsoft.com/en-us/windows/gg491725(v=vs.60)

The corresponding Windows 10 UWP API that windows web apps can use is:
https://docs.microsoft.com/en-us/uwp/api/windows.ui.startscreen.jumplist

Windows has the ability for apps to populate both static and "dynamic" deep link lists with custom category names, which is useful when you have the screen real estate. This overlaps with @mgiuca's proposal.

Let's be careful to define these things in a UX-agnostic way. These are definitely useful in any launcher UX outside of context menus; you can imagine multiple different ways to display these on a home screen. However, you want more than just an icon and display name; you want essentially everything the app manifest itself has--multiple icon sizes, background color, etc. So for standardization, maybe it's helpful to think of "shortcuts" as separate apps, kind of like how Windows 10 "secondary tiles" work:

https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/secondary-tiles

iOS 11 takes this even further by allowing widgets within the context menus below the deep links list.





-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/582#issuecomment-399142729