Quote:
Originally Posted by stumped
slightly off topic, but will that affect all android reader apps that could previously directly bwose G drive, or is it aimed just at you  |
Short answer: no.
Longer answer: the change isn't to GDrive, but is instead to Google authentication (OAUTH2). A person using an app must somehow authenticate with Google in order to use any Google service: calendar, mail, drive, photos, and so on. Google wants to prevent (discourage) apps from using an embedded web browser to authenticate and retrieve the access tokens. Their claim is that it isn't the optimal user experience, which is perhaps true. Unfortunately their "suggested approaches" are some combination of:
- not cross provider. They work only with Google authentication.
- not supporting android back to 4.0
- not working at all on devices without Google Services (e.g., Fire, many e-ink readers).
- not program-architecture compatible, meaning implementation is hard.
which means that CC cannot use them without significant unpleasant side effects, either to me (lots (!) of work), to CC users, or both.
I am not sure what the "real" reasons are for the change. I doubt that it is the stated reason, but is instead an attempt to build a higher wall around their garden.
I have no idea how many apps this change effects. From the recent chatter on the web, the number isn't small.