A substantive Techincal Manual is required: Current support provided by DIY Q&A plus blogs is inadequate.
Proton Drive really needs a proper technical manual, support is a basically a collection blogs and brochure style of articles how to do and fix stuff. That style of support is useful but has limitations.
High level glossy brochures and white papers are time wasters for thorough product evaluation. If a business is going to invest money and time into a product a technical user manual is the best place to start. Home users are no different.
The current idea of a user searching to solve a problem assumes users are asking the correct questions, that can lead to lot of user frustration by going down rabbit holes.
Manuals usually includes things like:
* Product limitations
* How it works. Example: I couldn’t find any explanation in support on the importance of cloud files (aka stub files) files and how they work.
* Things to avoid. Example: I could not find any explanation why you should avoid your ProtonDrive folder in backups. A backup app will trigger the download of everything in the PD folder.
Generating support tickets via the app is time consuming and having a proper technical manual would reduce the workload of the service desk.