Re: [w3c/manifest] Additional property to define a webapp to be single instance (single-tab) (#479)

I disagree with your conclusion that there is no need for a signle tab feature. 

As you say there is no need to specify a multiple tabs feature for web apps because this behaviour is the only one which exists today. For the most apps this is just fine because they just don't care about how many tabs the user has opened. Some apps even make use of multiple tabs. But there is really no argument to say that all web apps of the future should be designed this way.

Instead I would like to argue why a single tab feature is needed and required to be supported by the spec from my perspective:
1. There is no single tab feature today which makes this feature needed in the first place
2. I have a real business case for an realtime web app which is intended to be used on mobile phones only and for a timeframe of 3 minutes (timeout of the app). Users can relaunch this app during the execution of the app for the purpose of reconnection and they can launch the app after the timeout again. Anyway this app should exist only in one tab. (You can ask questions about this app but details of the business case have stay secret)
3. The single tab feature might also prevent resource wasting which is commonly known to be best practice on mobile phones

---
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/479#issuecomment-237243405