Imagine explaining this to your insert-technologically-inept-relative-of-choice.
"No no no, if it's a Word file you need to click on the hollow yellow-blue-and-green circle to edit it, if it's a native google document you need to click on the hollow yellow-blue-and-green hexagon to edit it."
"You don't know what type of document it is? No problem, you can tell by... Open it up in one of the two apps and tell me what the file extension is. The file extension. The three of four letters at the end. Wait a sec, forget that, native google docs documents don't have file extensions."
["Well, does the icon look like--no, never mind, the icon is the same for both, four white lines in a blue square." - I was wrong about this, word files do have a different icon]
"Umm, well, open it in one of them, and if you can't edit it, open it in the other one."
"Hold on, I'll drive over..."
"If you need to edit things in Drive, use the Drive app."
There are some use cases where the QO app makes sense, but its solving a fairly narrow problem that doesn't apply to most users.
> Well, does the icon look like--no, never mind, the icon is the same for both, four white lines in a blue square
What are you talking about? The icon for Word files in both the QO UI and the Drive app UI is a big blue W on a white square, and is nothing like the 3-long-1-short white lines on a blue square icon for Google Documents.
> Umm, well, open it in one of them, and if you can't edit it, open it in the other one.
The Drive edits Doc/Docx files; if for some reason you don't like using the Drive App to do that, you can switch to QO from the document opened in Drive by using the "Open in..." menu from Drive to open a document in QO.
which i'm sure is exactly what google wants. they want you creating documents in their format, not in microsoft's format. quickoffice exists to tick off the "MS Office compatibility" checkbox on spec sheets, not because google loves that file format so much. and office documents don't get the realtime collaborative editing or chat interface or any of the other stuff that drive documents get, so to reduce confusion about why some features are unavailable, it makes sense to keep it as a separate app.
Reading the basic description of what an app is is not equivalent to reading a manual.
