Understanding the authorization flow with Google Drive and Google Play Services -


i have gone through quickstart google drive , have used google play services. docs google drive outline process of how authorization flow works. docs indicate developers should not use drive initiated authorization although appears quickstart sample app that. left impression google prefers developer handle details of authorization.

yet after trying out sample code uses google play services (but not google drive), left impression google wants developers use google play services handle authorization. seems google play services simplify authorization process significantly. although docs don't this, found elsewhere online googleauthutil.gettoken manages how access , refresh tokens retrieved, after expire.

basically, issue struggling understand whether google drive docs api out of date , google wants rely upon google play services. there seems lot of complexity in google drive authorization process google play services has eliminated. @ same time, docs google drive api has been available on half year, makes me question why google hasn't updated these docs show reflection on how google play services used it.

any insight appreciated.

the recommended approach authorization on android using google play services. android quickstart guide on google drive sdk documentation covers that:

https://developers.google.com/drive/quickstart-android


Comments