The more I use the Chromebook Files app, the more I am upset by its peculiarities

I had a long discussion recently about the Chromebook’s Files app’s lack of functionality compared to its Web Drive app. Obviously, this can be seen with the missing Workspaces feature which allows workspace users to place files in a special group for editing with a quick recall, in the same way as placing a pile of papers on a physical table. While probably not vital for most people, I found this to be an odd exclusion.
I understand the app itself is still largely in development and gaining new features every month including new compression or archiving tools. However, the more I try to integrate the local system web app built into Chrome OS into my daily workflow, the less capable I find it.
Today I noticed something strange that made it impossible for me to use it. I went to open a Word .docx file from my Drive through the Files app so that I could make suggestions for changes. I normally do this from Drive on the web out of habit, but figured I’d try to give my device a more traditional feel by using the Files app to find and open items instead.
To my surprise, the Word file opened in Office Compatibility Mode! For those who don’t know, this stripped-down version of Google Docs allows users to edit .doc and .docx files while retaining their formatting, but in return, you are provided with almost no tools or functionality compared. to those who exist in the full fledged Google Docs experience.
In 2019, Google created something called âNative Office Editing,â and while it wasn’t publicly referred to as such, it was a way you could open these types of Microsoft Office files in Docs, Sheets and Slides, keep their original file type and retain more precise formatting than Office Compatibility Mode, while still being able to edit with the full suite of tools available in the company’s own editing tools. business !
Google said that you can only use this new editing mode if you upload your documents to Drive before opening them, along with all files opened from a local source like your hard drive, USB drive, etc. using Office Editing for Docs, Sheets, and the Slides extension, would still open in the old-fashioned Office Compatibility Mode, but that’s where we have a problem.
When opening Word files from the Files app on my Chromebook, the items that were forced into Limited and Shabby Office Compatibility Mode were actually files that reside in my Drive! This means that the local app cannot apply the same special privileges to files as Drive on the web. This ultimately makes the Files app unnecessary for anyone who wants to have full editing capabilities with their imported Office files while still using a file manager that doesn’t feel stuck in a web browser.
Because of this, I constantly find myself coming back to Drive on the web, and it’s just plain disappointing. No matter how much more appealing Google makes the local app to use (the new white theme is part of its âFiles App Next Generationâ brand), it’s still drab, and unacceptable to me. For something so important, Google would have to have a feature parity standard for its products before they roll out in mass. “Half Baked” and “Forever Beta” should just be the motto
Some may say I’m nitpicking, and admit that with the workspaces issue this was something that was probably going to be a non-issue for 99% of users, but this weird inconsistency with Word files looks like an obvious lack of Google on behalf of. Have you been through this, or are you just noticing it now that I mention it? What other features do you think are essential for your use that are currently lacking?