PWAs won't work for every use case, and can make some more difficult. However, ChromeOS _tends_ to support Android applications, so they're where the replacemen

PWAs won't work for every use case, and can make some more difficult. However, ChromeOS _tends_ to support Android applications, so they're where the replacement lies. 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.