7 ms·

Chrome Apps were a Chrome-only proprietary solution, and they're being replaced by Progressive Web Apps which work in other browsers as well. This is the sort o

by jefftk 7y ago

Chrome Apps were a Chrome-only proprietary solution, and they're being replaced by Progressive Web Apps which work in other browsers as well. This is the sort of change we should be supporting! (Disclosure: I work at Google, not on Chrome)

ilrwbwrkhv 7y ago
No I don't support pwas either.
- rpastuszak 7y ago
  Why?
- nolok 7y ago
  Do you support X or support Y is not really what was being talked about, the question is from a starting point of X existing do you support it moving to Y (instead of remaining X). Moving from a proprietary to a shared/common system is an obvious move forward.
pier25 7y ago
So PWAs will have support for Bluetooth and all the other features of Chrome apps?
- dragonwriter 7y ago
  That's the broad idea of Google's Web Capabilities effort, “There are some apps that are not possible to build and deliver on the open web today. We call this, the app gap. The gap between what’s possible on the web and what’s possible on native. We want to close that gap. We believe web apps should be able to do anything native apps can.” https://developers.google.com/web/updates/capabilities https://developers.google.com/web/updates/capabilities
  - pier25 7y ago
    > We believe web apps should be able to do anything native apps can It's a nice sentiment. Time will tell how that turns out.
- Andrex 7y ago
  https://developers.chrome.com/apps/migration https://developers.chrome.com/apps/migration Everything except advanced File System APIs are supported by PWAs, including Bluetooth through the Web Bluetooth API. [1] The replacement Native File System API is in origin trial and is pre-standardization, however. [2] [1] https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web https://developers.google.com/web/updates/2015/07/interact-w... [2] https://web.dev/native-file-system/ https://web.dev/native-file-system/
  - magila 7y ago
    Another big gap is the sockets API. Chrome apps have direct access to TCP and UDP sockets. PWAs can't have this for obvious reasons.
    - Andrex 7y ago
      Good catch, and the migration page kinda glosses over that. They are asking for input and use cases, though. "Q: My app uses the chrome sockets API to do networking. Can this be done with the open web? You might be able to do what you need with WebSockets. However, to use this, you will likely need to change the remote end of your connection. If that isn't possible, we'd like to hear more about your use case—please let us know about what you're trying to accomplish via the Chromium issue tracker.[1]" 1. https://bit.ly/new-fugu-request https://bit.ly/new-fugu-request
      - ronsor 7y ago
        This is bad. Simple TCP and UDP sockets are the foundation of the internet.
        Andrex 7y ago
        Correct, but they are not the foundation of the Web -- HTTP is, and web specification writers are only concerned with creating APIs for the web platform (hence why Web Sockets is an upgraded HTTP connection, not lower level like raw TCP or UDP.)

by jefftk 7y ago

ilrwbwrkhv 7y ago

No I don't support pwas either.

rpastuszak 7y ago
Why?
nolok 7y ago
Do you support X or support Y is not really what was being talked about, the question is from a starting point of X existing do you support it moving to Y (instead of remaining X). Moving from a proprietary to a shared/common system is an obvious move forward.

pier25 7y ago

So PWAs will have support for Bluetooth and all the other features of Chrome apps?

dragonwriter 7y ago
That's the broad idea of Google's Web Capabilities effort, “There are some apps that are not possible to build and deliver on the open web today. We call this, the app gap. The gap between what’s possible on the web and what’s possible on native. We want to close that gap. We believe web apps should be able to do anything native apps can.” https://developers.google.com/web/updates/capabilities https://developers.google.com/web/updates/capabilities
- pier25 7y ago
  > We believe web apps should be able to do anything native apps can It's a nice sentiment. Time will tell how that turns out.
Andrex 7y ago
https://developers.chrome.com/apps/migration https://developers.chrome.com/apps/migration Everything except advanced File System APIs are supported by PWAs, including Bluetooth through the Web Bluetooth API. [1] The replacement Native File System API is in origin trial and is pre-standardization, however. [2] [1] https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web https://developers.google.com/web/updates/2015/07/interact-w... [2] https://web.dev/native-file-system/ https://web.dev/native-file-system/
- magila 7y ago
  Another big gap is the sockets API. Chrome apps have direct access to TCP and UDP sockets. PWAs can't have this for obvious reasons.
  - Andrex 7y ago
    Good catch, and the migration page kinda glosses over that. They are asking for input and use cases, though. "Q: My app uses the chrome sockets API to do networking. Can this be done with the open web? You might be able to do what you need with WebSockets. However, to use this, you will likely need to change the remote end of your connection. If that isn't possible, we'd like to hear more about your use case—please let us know about what you're trying to accomplish via the Chromium issue tracker.[1]" 1. https://bit.ly/new-fugu-request https://bit.ly/new-fugu-request
    - ronsor 7y ago
      This is bad. Simple TCP and UDP sockets are the foundation of the internet.
      - Andrex 7y ago
        Correct, but they are not the foundation of the Web -- HTTP is, and web specification writers are only concerned with creating APIs for the web platform (hence why Web Sockets is an upgraded HTTP connection, not lower level like raw TCP or UDP.)