6 ms·

PWA in Windows 10 can access the same APIs as UWP C# & C++ apps https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps/windows-features https://do

by yrio 8y ago

PWA in Windows 10 can access the same APIs as UWP C# & C++ apps https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps/windows-features https://docs.microsoft.com/en-us/microsoft-edge/progressive-.... I don't know about Android / ChromeOS.

pjmlp 8y ago
On ChromeOS you get access to these extra APIs, as it is a browser based OS. They have only been dropped for Chrome Apps. https://developer.chrome.com/apps/api_index https://developer.chrome.com/apps/api_index As for Android, the "What Web Can Do" PWA displays what extensions are currently available, https://whatwebcando.today/ https://whatwebcando.today/
- skybrian 8y ago
  Those are useful links but are they don't give PWA's the same rights as native apps. Chrome apps do use HTML and JavaScript but aren't PWA's. The API's and sandboxing is different. There are many useful HTML5 API's, but they don't require code signing as far as I know, and they don't have the same permissions as Android apps. (The permission system is entirely different.)
  - pjmlp 8y ago
    You are missing an important thing on how PWA are supposed to be coded. PWAs are supposed to check the avaialbe sandbox APIs and adapt accordingly. So if a PWA is running on Windows on an UWP context, it can check it and then access UWP APIs, if they are running on Chrome OS instead, then check accordingly and act upon it. Finally if only play old HTML 5 APIs are available, then make the best of it. That is the whole point of Progressive, to enhance the experience depending on the surrounding context.
    - cruise9 8y ago
      I thought the point of PWA would be ‘free’ compatibility with every OS that can run PWA. Checking for several different APIs and using the appropriate one seems counter to this.
      - pjmlp 8y ago
        The point of PWAs is to offer native like experiences with web technologies if you pay attention to talks done by Chrome/ChromeOS/UWP teams. Browser specific APIs are a thing since the Web became a platform instead of plain hypertext documents.

by yrio 8y ago

pjmlp 8y ago

On ChromeOS you get access to these extra APIs, as it is a browser based OS. They have only been dropped for Chrome Apps. https://developer.chrome.com/apps/api_index https://developer.chrome.com/apps/api_index As for Android, the "What Web Can Do" PWA displays what extensions are currently available, https://whatwebcando.today/ https://whatwebcando.today/

skybrian 8y ago
Those are useful links but are they don't give PWA's the same rights as native apps. Chrome apps do use HTML and JavaScript but aren't PWA's. The API's and sandboxing is different. There are many useful HTML5 API's, but they don't require code signing as far as I know, and they don't have the same permissions as Android apps. (The permission system is entirely different.)
- pjmlp 8y ago
  You are missing an important thing on how PWA are supposed to be coded. PWAs are supposed to check the avaialbe sandbox APIs and adapt accordingly. So if a PWA is running on Windows on an UWP context, it can check it and then access UWP APIs, if they are running on Chrome OS instead, then check accordingly and act upon it. Finally if only play old HTML 5 APIs are available, then make the best of it. That is the whole point of Progressive, to enhance the experience depending on the surrounding context.
  - cruise9 8y ago
    I thought the point of PWA would be ‘free’ compatibility with every OS that can run PWA. Checking for several different APIs and using the appropriate one seems counter to this.
    - pjmlp 8y ago
      The point of PWAs is to offer native like experiences with web technologies if you pay attention to talks done by Chrome/ChromeOS/UWP teams. Browser specific APIs are a thing since the Web became a platform instead of plain hypertext documents.