Re: [w3c/manifest] Add a manifest option for the declaration of the web application running pattern (Issue #1019)

> A similar question came up in the context of [Tabbed Application Mode](https://github.com/w3c/manifest/issues/737#issuecomment-779760941).

Thank you for your response.

While, of course, the tabbed-view is a nice thing to have in [#737](https://github.com/w3c/manifest/issues/737) and the new data storage model you mentioned there, I believed as an experienced developer, is a keystone for expanding the ability of web applications. 

However, we are addressing two related but not identical problems. The tabbed-view function and LocalStorage is mostly focused on the UI and data storage side of the PWA development. My proposal is advocating adding new **support for single-instance-only PWAs from browser-level** (i.e browsers would forbid launching new instances if there is already a running single-instance-only pwa). And I don't think adding a tabbed view option to the display member would be the solution for the problem I mentioned in this proposal. Because, a single-instance-only PWA may or may not use tabbed view and the LocalStorage but our browsers need a direct way to know what type this application is and PWA developers should also have a direct way to acknowledge the browsers that their application should and can only have one running instances.

The [Sudoku game](https://sudoku.jull.dev/) scenario is just to illustrate that this type of PWA should not have multi-instance operation mentioned in the proposal, rather than to achieve the purpose of multi-instance data separation.

-- 
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/1019#issuecomment-953705648