Or in other words, give _Chromebooks_ file associations.
https://developers.google.com/drive/v1/reference/
They should have definitely not hidden it so far away.
> Warning: Apps will not have any API access to files unless the app has been installed in Chrome Web Store. To test an app during development, you must first create a listing and install it.
B) Application developers can use an SDK to go directly to your Drive account, and do some extra tricks.
https://code.google.com/p/google-api-go-client/source/browse...
There is a sample .NET app for GDrive: https://developers.google.com/drive/examples/dotnet
If this is the case, then a native app could exist Chrome Web Store solely for the purpose of letting users authorize the app to access their GDrive.
I must be missing something obvious :)