> The Google Drive API includes a special hidden folder that your app can use to store application data.
Again, that means a user cannot drop their files into a special app folder for processing. It does not facilitate the simple use case of creating an App to distribute purchase orders to vendors.
But your application could store them there... I don't think the use case most users are looking for is to have a magic Drive folder that automatically processes purchase orders when they're added.
That's also not what the parent comment I commented on was referring to.
I think it is a very common use case to have a folder for an app that will do something and not have an app need permission to your entire folder. But google doesn't think so. You had responded to my comment which talked about such a use case.
I think it is obvious that purchase orders are an example. Have temporary hidden storage via an application data folder may be useful, but I am talking about folder level permissions for an app.
Again, that means a user cannot drop their files into a special app folder for processing. It does not facilitate the simple use case of creating an App to distribute purchase orders to vendors.