Access to files is the critical issue here. Look at these examples from the article:<p>> <i>Chrome OS doesn't have a robust photo editor? Don't worry, you can download an [Android] app! Chrome doesn't have native integration with cloud file services like Box, Dropbox, or OneDrive? Just download the app! Chrome doesn't have Microsoft Office? App!</i><p>The problem is that Chrome OS is attempting to be a <i>desktop</i> platform, using web apps and mobile apps.<p>Desktop OSes (Windows, macOS) are all about files. Apps are files. Your documents, photos, and videos are files. Any app can access any of your files.<p>On mobile, you don't normally interact with files. Apps aren't files; you launch apps directly from the app launcher, and they store data internally; when you delete an app, its data is deleted, too.<p>Web apps are like mobile apps: they don't have access to your files. You can't make a web app photo editor that opens a file, makes some changes, and then saves those changes to the file. Instead, you have to "upload" the file to the web app, and then you have to "download" the modified file.<p>Microsoft Office has a web version (Office 365), but it's like Google Docs, lacking access to your local files. Dropbox has a web app, but it just lets you download files one at a time; it's impossible to implement Dropbox-like file synchronization in a web app.<p>Google is aware of this problem, but you might not like their proposed "solution," to develop a cross-browser standard file access API. <a href="https://web.dev/native-file-system/" rel="nofollow">https://web.dev/native-file-system/</a> Google's currently running an "origin trial," where a small number of web sites have temporary access to the feature to try it out.<p>I think Google's not going to ship it until they convince Apple or Mozilla to approve; it's not clear when (or if) that will happen. Here's the most recent discussion from May. <a href="https://github.com/mozilla/standards-positions/issues/154" rel="nofollow">https://github.com/mozilla/standards-positions/issues/154</a><p>So file access isn't technically "stalled out," but it's still going to take a long, long time.