I have a google drive account that i want people within a certain organization to be able to upload files to programmatically, and also as invisible as possible. as i'm following along the google drive SDK tutorials, i can't seem to find anything about uploading a file directly to MY drive account. all the tutorials seem to be talking about allowing users to upload a file to their own account. The other problem is that they seem to all require some user permission (which i don't want).
the idea is this -> there's about 100 ppl (very controlled on who gets access) that have a special build of an android/iOS build, and for these people, i want to periodically sample certain screenshots of how they use the app. i'm able to save the screenshot files to their device locally; however, i want a "semi-public" source of viewing on these files. so i've set up a google drive account so that i can accept these screenshots in to my account. however, i don't want the users to have to accept any permissions, or use their own account. Ideally, at the end, i can share my drive account folder (with these screenshots) with people that i select to share it with.
Is this even possible? If so, how do i do this?
The Drive API for Android only supports authorizing the current user, however if you use the Google APIs Java client instead to access the Drive API you can store credentials for your account with the application and use those for all users of your app. Read more about authorization and the Java client here.
Related
I am developer, selling my apps.
But I dont always have access to my PC, so I was thinking writing a simple app which would access my Wallet Account to see how much I earned this day/week/month.
Is there any API and some working example how to do this? THanks
Do you know about the official Play console app? It lets you check financial data among other things, like reply to reviews.
If you do need programmatic access there isn't an API, but you can Download reports from Google Cloud Storage which has an API. There are instructions on that page for both a command line tool access and a client library and service account.
I'm trying to develop android app something like "Notes". The idea is to ask user to sign in to his google account and use his drive space to store his notes. Simply user should have his data with him & should pay for storage if necessary. Also in future this should work for Windows, iOS.
Till now, I have discovered Drive API and I'm confused. Its is showing 'me' the billing options.
Any idea?
the billing options you see are for your console project. you wont need to enable billing unless you will use up the daily quotas. the free quotas are very large, in the millions of calls per day. those quotas are not related to the space your files will use in each user's drive. they just refer to your right to call the apis with your console keys.
I'm not sure where you are seeing billing options, but the Drive API stores items in the user's Drive using the user's quota.
I am developing an android app which offers in-app purchases. The content I want to sell is media files like images and audio files. I would like to implement a mechanism to download those files from an external server (maybe Google App Engine could be helpful) after the user has paid for a file.
My concerns are:
I want to make the mechanism independent of the amount of files I want to sell. This means that adding new content to the google play console should not require any update of my app.
How to protect any kind of URL on the device side that gives any clue about where the content is hosted?
Has anyone done something similar already? Could you please help me?
Note - my experience is with a previous version of Google's IAP. I assume what I say below still works but have yet to upgrade my app.
1) Have your application contact your server for the list of products for sale. Note that your play account will have to contain an entry for each element offered in order to give pricing and description information.
2) You cannot protect the URL. What you can do is protect the content. As part of the request to get the information, you should pass receipt information that can be verified at the server (see Google docs) before allowing access. Might also want to think about things like nonces and other security techniques to prevent replays.
I am making and android app which downloads a particular file from Google Drive, reformats the data in the file and then displays it to the user.I have used the Google Drive API. In the app, instead of asking the User to select an account, I want to hard code a Google Account Username and Password through which the file on the Drive is downloaded. This should happen without the user's interaction.
You do not need to hardcode your account data - just use Service account
How to use Google Drive SDK in Android project with hardcoded credentials - here the solution.
I'm developing an android application.
In the android application, users read files from my google cloud storage and also update files to it, although it is not the main purpose of the application.
Now, I'm quite confused about how I allow users access to my google cloud storage.
Google recommends to use OAutn 2.0 authentication. So, I treid how it works on the following site.
https://developers.google.com/oauthplayground/
In the playground, I allowed the "oauthplayground" to access to my google cloud storage.
But I don't need this step because I always want to allow the android application to access to my google cloud storage.
After thinking, I had the idea to use the Authorization code for the android application to access to my google cloud storage.
But it was a bad idea because an Authorization code has the expiration time.
How I allow users to access to my google cloud storage in this case??
Please help me.
If privacy is not a concern, you could set the ACL on the bucket to public-write. If privacy is a concern, you can use the Signed URLs feature. You can find an example of using the Signed URLs feature in the storage-signedurls-python repository on GitHub.