I'm building an app on android that has the features of Log-in with facebook and Log-in with Google. Assuming the user chooses to login with google, I would like to ask for permission and collect basic information such as name,age,sex,location,email from his profile and save it on my server's database.
Here is the problem: Which api should I actually use to grab these info? I don't think google+ api would be a proper choice since not every google user has one. After checking Google-api-java-client documentation, I still cant find anything useful.
There seem to be no library for this basic operation.
The only thing that seems relevant is Google Apps Profile API but
1. it's outdated.
2. Its not free.
I'm too confused and I hope someone can guide me through this nightmare.
Edit: found some new relevant info but I'm still hoping to find an official java library for this:
https://oauthssodemo.appspot.com/step/1
Found what I was looking for: http://javadoc.google-api-java-client.googlecode.com/hg-history/c35433d3077dc4eb89dccb25618dc70dbd375d65/apis/oauth2/v2/com/google/api/services/oauth2/model/Userinfo.html
Related
I am trying to develop an app which needs to access google developer API by using developer email.I have gone through official documentation.I don't understand much.I created client id by following this instructions.https://developers.google.com/android-publisher/authorization
But for generating token they mentioned to call this API "https://accounts.google.com/o/oauth2/auth?scope=https://www.googleapis.com/auth/androidpublisher&response_type=code&access_type=offline&redirect_uri=...&client_id=...".I have client id but I don't know the value for redirect URI in case of android application.objective is I need to get all reviews of the app from developer credentials.Pls anyone help.Thanks in advance
If you don't know what you are doing, you might find it useful to look at the code samples
According to this documentation adding a publish permission to my android application, it uses Session class which is deprecated now. Can anyone tell me what is the updated way to achieve this? I want to post something on the user's wall with my app. And I found this is the way to post something on user's wall, to simply make a POST call on this url:
graph.facebook.com
/{user-id}/feed?
message={message}&
access_token={access-token}
Is this the correct way or is this somehow deprecated too?
I don't see the word "Session" occur on the page you are referring to.
Regardless, you can read the "Sharing on Android" docs page to learn how you can publish content from Android devices.
The recommended way of doing this is by using the share dialog, because that does not require users to grant any publishing permissions. Since you have to include the SDK anyway in order to implement Facebook login, you might as well make use of this feature.
Like how I tried to effectively word in the title, my issue with Sign-ups and log-ins for my application is that it would work best with a college email, as it's an app designed for college campuses, but I can only find APIs and information regarding the Google+ sign-up that is everywhere.
For instance, an app like Kik does not require a Google+ sign-in and you can make your account however you like, but I've not found any information on how to go about creating a sign-in like that. The only substantial information regarding sign-ups/log-ins I've found are for the Google+ API.
The only other thing i thought of was using the Google+ sign-in to verify the person, and then having something in the settings to enter and save the college email for the uses it'll have.
Would any of you have thoughts on this? I'd prefer not to do the latter simply because it requires more for set-up of the app on the users part (which isn't ideal) to use it's full functionality, but I don't really see any other way of doing it at this point.
I don't know what you guys think, but I believe that the Facebook SDK documentation is very limited and doesn't explain very much; Luckily throughout the use of some videos I was able to set up most of the integration that I needed.
However my application doesn't interact with just Facebook friends. It interacts with anyone and everyone using the application. Meaning if Jim and Sally aren't facebook friends, they can still see each-others profile picture, age, and name.
I'm not asking for you guys to write this out for me, but a nudge in the right direction would be lovely, perhaps accompanied by a link.
There is no API to "get all App users", you would have to store each user in your own database. Of course you have to deal with users deauthorizing your App - you can do that with the "Deauthorize Callback URL" in the advanced settings of your App.
I'm searching for a tutorial or an explanation on how to remove advertisement in my application with in-app purchase?
I will put some ads with ad-mob in my app but I also want, that the user can disable the ads when he pays a little donation. Do you know a site or tutorial where I can find a step-by-step explanation how to do this?
Or do I need to publish 2 versions of my app? One with ads and one without ads for paying?
Don't use the SharedPreferences method because if the user flushes the app data or uninstalls/reinstalls your app their ad-free status will be lost.
A couple of ideas:
If your app has any kind of web based login or authorization, you can flag the user as having bought the ad free version by updating the web database's customer data and then disable ads in code following login and verification. This has the added benefit of following the user to new devices.
Use one of the several ways to get a unique device id, and store that in a web server database. On startup, query the DB to see if the device is ad-free. See Android Unique Device ID. This will only work for that particular device though.
The two apps approach is simple enough to get the job done too. :)
This presentation seems to explain an example and includes a link to source code at github:
http://gotocon.com/dl/2011/GeekNights/Tjen_penge_p%C3%A5_Android_ARH.pdf .
It stores the purchased upgrade at a sharedpreference.
However, I'm still looking for a more secure and robust solution that works out the use-case explained here:
http://vlingo-en.custhelp.com/app/answers/detail/a_id/1785/~/moving-in-app-purchase-(ad-removal)-to-new-android-phone/p/180