I hope not! Outside of the Chrome part, ChromeOS is a mess of awkwardly attached virtual machines. If you want a "native" app (unless your native app is Steam),

I hope not! Outside of the Chrome part, ChromeOS is a mess of awkwardly attached virtual machines. If you want a "native" app (unless your native app is Steam), your best option is Android, which means you're inside an Android VM, your webview component is an Android Chrome webview, you can't see other things on the network (because you have a virtual network device), permissions are granted via the Android Settings panel which is distinct from the Chrome OS Settings panel and an even more user-hostile experience than it already was, and your widgets are all slightly wrong. It is bloat all the way down. Running plain old Linux apps is a similar problem, except it's a "developer feature", so you can't expect an end user to use your app on their Chromebook. It is exceedingly difficult for a developer to contribute any kind of improvement to this because the bug tracker is a black hole and the source code is a gargantuan monorepo with multi-page build instructions that basically require you to sacrifice a computer if you want to get anywhere. Sandboxing is great and all, but the thing is a glorified hypervisor. It has no vision of its own for app distribution, user experience, or developer experience. It boggles my mind that they are doing this with ChromeOS: the OS that runs on the cheapest, slowest, most under-specced computers on the market.