Re:Google Drive SDK
by haberman on Tuesday April 24, 2012 @04:17PM
(#3886134)
My reading of this is that the Chrome Web Store is where apps are listed and users authorize them, but not necessarily that the app has to run in a web browser. The user could authorize the app by "installing" it through the Chrome Web Store but download/use it from a totally different channel.
PS: I work at Google but don't have any inside info on this.
Re:Google Drive SDK
by haberman on Wednesday April 25, 2012 @11:16AM
(#3889446)
I understand that. There's no way to have the web store install a native app.
But once you have "installed" the web app, how would the API server have any idea whether a Google Drive API request was coming from a web server, some JavaScript running in a web browser, an Android app, or a remote island in the Pacific that has no electricity via the "IP over Avian Carriers" protocol? It's just HTTP requests with some authorization headers that tie it to your app's identity.
Re:Google Drive SDK
by VikingCoder on Tuesday April 24, 2012 @03:25PM
(#3885869)
Google Drive synchs to your local hard drive, and thus works with all of your apps. (Right?)
It ALSO has a Chrome interface to be clever. Picture opening a 1,000 page PDF. If the Chrome PDF Viewer knows how to fetch individual pages on demand, do searches on the server side, etc., it could be very nice for quick previews, etc.
Also, it works great for one content creator (who has the app on the desktop), and a bunch of content viewers (and commenters) who just need Chrome.
Re:Google Drive SDK
by option_greek on Tuesday April 24, 2012 @04:57PM
(#3886296)
I think its a pretty stupid move. If they really want developers to flock to Google drive, they should not limit the api to their little corner of the world. I'm guessing that they are going to open it to all apps eventually.
> 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.
Re:Google Drive SDK
by haberman on Tuesday April 24, 2012 @04:14PM
(#3886121)
It looks like the Chrome Web Store is the centralized place for developers to list apps and for users to authorize them. But once the app is registered/authorized, I'm not sure how the server would have any idea whether requests were coming from a web app or a desktop app.
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.
Re:Google Drive SDK
by SiVal on Wednesday April 25, 2012 @05:12AM
(#3888274)
It's interesting that on the About Google Drive page, they claim, "Data is inherently social."
Funny, I claim that my data is inherently private. Is it a coincidence that companies that would like to sell my data have the philosophy that my data is "inherently social"?
Re:Google Drive SDK
by cleverjake on Tuesday April 24, 2012 @01:09PM
(#3885031)
"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."
While that does make it feel a bit more secure, that would be a huge hassel for anyone that wants to go stealth at first.
Re:Google Drive SDK
by etrain on Tuesday April 24, 2012 @01:35PM
(#3885208)
Yeah, this seems kind of bogus - if I'm reading it right, you also have to be creating a webapp to use their API - so hope of implementing a Linux client on FUSE is low at this point.
Re:Google Drive SDK
by willscott on Tuesday April 24, 2012 @02:13PM
(#3885473)
It seems like a better candidate for a linux FUSE client would be the existing document list API. It works with oauth, and lets you interact with documents.
The Drive API is a way to integrate new editor types into google docs.
Re:Google Drive SDK
by skore on Wednesday April 25, 2012 @05:32AM
(#3888329)
Even though I knew about Google Drive, my brain somewhat zoned out for a second and - probably under the influence of yesterdays Planetary Resources Announcement - I thought Google was releasing an SDK for autonomous cars.
Re:Google Drive SDK
by bashzor on Tuesday April 24, 2012 @02:18PM
(#3885512)
I wish people stopped flooding Hacker News with the same product. Or even more so, upvoting all five on the homepage alone. It's not like Drive is that great. Actually it very much pales next to Dropbox.
Re:Google Drive SDK
by Newky on Tuesday April 24, 2012 @02:29PM
(#3885577)
In some areas perhaps it hasn't got some of the functionality that Dropbox has, but it also seems to be scratching a lot of itches which Dropbox isn't even considering scratching.
This is not to say Dropbox should consider. Just I don't think you could say this offering pales in comparison to Dropbox. The app SDK in particular looks exciting.
Re:Google Drive SDK
by huggyface on Tuesday April 24, 2012 @02:36PM
(#3885617)
It's not like Drive is that great. Actually it very much pales next to Dropbox.
That sounds remarkably sour. Nonetheless, it gets attention because it had been talked about for literally years (back to the latter 2000s). On the day of release it isn't super surprising that it's getting some love.
PS: Yes, I work on the SkyDrive developer platform. It doesn't change the truth.
PS: I work at Google but don't have any inside info on this.
But once you have "installed" the web app, how would the API server have any idea whether a Google Drive API request was coming from a web server, some JavaScript running in a web browser, an Android app, or a remote island in the Pacific that has no electricity via the "IP over Avian Carriers" protocol? It's just HTTP requests with some authorization headers that tie it to your app's identity.
It ALSO has a Chrome interface to be clever. Picture opening a 1,000 page PDF. If the Chrome PDF Viewer knows how to fetch individual pages on demand, do searches on the server side, etc., it could be very nice for quick previews, etc.
Also, it works great for one content creator (who has the app on the desktop), and a bunch of content viewers (and commenters) who just need Chrome.
I must be missing something obvious :)
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.
Funny, I claim that my data is inherently private. Is it a coincidence that companies that would like to sell my data have the philosophy that my data is "inherently social"?
While that does make it feel a bit more secure, that would be a huge hassel for anyone that wants to go stealth at first.
Chrome Web Store has an option for testing where you can whitelist authorised people by Google ID. It may not address the whole issue, but it helps.
I wish google would try being different than apple rather than the same.
The Drive API is a way to integrate new editor types into google docs.
This is not to say Dropbox should consider. Just I don't think you could say this offering pales in comparison to Dropbox. The app SDK in particular looks exciting.
That sounds remarkably sour. Nonetheless, it gets attention because it had been talked about for literally years (back to the latter 2000s). On the day of release it isn't super surprising that it's getting some love.