Google Gives Chrome OS Apps a Shutdown Date
arstechnica.com
arstechnica.com
- run offline (probably yes by caching ServiceWorkers)?
- use the Chrome App Store to provide additional assurance that I'm distributing the same code to everyone? (what if I distribute my app as an extension?)
- use compiled code through WASM? (I assume of course yes, and so I don't need PNaCl)
- access the network? or only protocols like HTTP that you can get to on the normal web? (again, what if I distribute my app as an extension?)
Unrelatedly, does the 2021 phaseout of PPAPI mean that PPAPI Flash is dead?
But, to answer some of your questions:
> - run offline (probably yes by caching ServiceWorkers)?
Yes. And that's how. Mostly via storage mechanisms for data, like localStorage or IndexedDB, or network mechanisms like the Cache API.
> - use compiled code through WASM? (I assume of course yes, and so I don't need PNaCl)
Yes, and you have been able to for a few years. I can't find the day the switch went over for ChromeOS in particular, but since at least 2017. There doesn't look like any plans to remove it, and that wouldn't make sense at this point.
- access the network? or only protocols like HTTP that you can get to on the normal web? (again, what if I distribute my app as an extension?)
JS tends to only speak HTTP/S and WebSockets. So far as I know, you don't have access to a raw socket with extensions. There are some ways to get FTP working, and other text-based protocols, but they're not guaranteed to always work, because they are workarounds.