That makes no sense - if you don't trust Google Drive, don't use it.
Google is not "forcing itself down the throat" with Google Drive, and even my Android phone comes with 3 cloud providers.
And yes, your apps certified Google as a trustable provider when they added support for it. Such support is not automatic, it requires non-trivial effort, and presumable no one would do it for services they do not trust.
> And yes, your apps certified Google as a trustable provider when they added support for it. Such support is not automatic, it requires non-trivial effort
Are you talking about the technical support (ie implementing APIs) or the bureaucratic support (ie going through Google's process) ? Because the first one is a result of Google going its own way with its own protocol, and the second is entirely a decision of Google.
> and presumable no one would do it for services they do not trust.
No, they would not do it for a service that is vital for the sustainability of their app. When Google is so hegemonic it's sometimes impossible to avoid, app developers must consider whether Google's ways are worth implementing not just based on Google but on the users' willing to make do with an app that doesn't work with Google. Not being compatible with Google is more often than not seen as a problem with the app, not with Google.
Google is not "forcing itself down the throat" with Google Drive, and even my Android phone comes with 3 cloud providers.
And yes, your apps certified Google as a trustable provider when they added support for it. Such support is not automatic, it requires non-trivial effort, and presumable no one would do it for services they do not trust.