- From: jfey <notifications@github.com>
- Date: Wed, 13 Mar 2019 10:23:17 +0000 (UTC)
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 13 March 2019 10:23:39 UTC
Hello again, The proposal was not about **permissions** etc - it was about **capabilities** and the matching/filter process. It would help to get the right app onto a device. The permission game is a different beast and works when the app is loaded and running. Agreed. Capability matching would help any discovery stage for complex/intelligent web components or app. I know - this kind of stuff is currently more oriented towards vertical/embedded solutions but it could also be of importance for mobile apps or TV sets. After browser based apps did loose against QT and other UI solutions big time in the past (i know this first hand) now time has come to come back to the browser based UI/UX approach. We are talking millions of devices - from kitchen appliances to smart home systems to ebikes to cars to infrastructure. Not all components of a solution may be known right at initial compile time - but there is still some need to discover newly available components and to add those during runtime in a dynamically fashion. Maybe i was not clear enough about the scope/impact/direction of the proposal. -- 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/756#issuecomment-472363815
Received on Wednesday, 13 March 2019 10:23:39 UTC