I'm looking for an easy way to get user's gender & age programmatically without any user input. I do not want to trouble the user with any sort of sign-ins to G+, FB or Twitter.
Just need a quick and easy way to get gender & age.
Is there any way to get user's gender and age without requiring any account sign-ins?
Are there any SDK's that would give this info without sign-ins?
There isn't any. You have interact with user to get the details, either by sign in or asking by yourself.
In some cases, you can however get some details, there is a contact, called as User which a few users fill. It might have the information you require but it is mostly empty.
But you shouldn't use this as it might be against user's will. You should use sign in or input fields.
If you are only looking for getting this information for statistical purposes, I'd recommend using Firebase analytics. Firebase automatically gives you age and gender distributions of your users.
https://firebase.google.com/docs/analytics/
You can't get any information without the user giving them to you (either with stating them in the app or giving you permission to take them). As #Sahil stated, IF the user has a contact with that information in order to take them you must get contacts permissions, which is not very smart having in mind that you only need users age and gender. The best way is to have a dialog or something similar where the user will state this informations.
Related
I need to fill data safety form in google play console. I have few doubts.
Name and email
Usually in android phones, the user logs in with a gmail id before starting to use the phone. This gmail id can be requested by the app like a permissions alert dialog. Now my doubt is, I am getting user's email id not like this but as a form submission. User types his email id. Now what should I mention in the data safety from. Should I mention as collecting or not collecting.
Location
Another similar doubt. I am not getting location using permissions. But the user types his zip code/pincode when adding his address. Should I mention collecting or not collecting.
Thank you in advance. If anyone needs more details, mention in comments and I will add it.
I think you can state both as collecting.
According to User Data
You must be transparent in how you handle user data (e.g., information collected from or about a user, including device information)
is going to be as data collection about the user.
I want to get a user id / Google id from a app user without Google sign in. Is it possible to identify a user without authentication?
I want to sync data between devices without a login.
Thank you for any tips like classes or anything else.
Is it possible to identify a user without authentication?
No. Identifying a user is basically the literal definition of "authentication". It's like asking if you can get wet without using a liquid.
Firebase SDK automatically collects some of the important and common user properties. Which can be found here.
In our app and website, we auto-detect the user's country. We also allow the user to change it to their preferred country if needed. We are using this country value for providing more localized content.
The current problem which we are facing now is, the auto-detected country is mostly the same as Firebase automatically select country (user property). But if the user manually changes the country to a different one in the app, the country in Firebase and app won't match. Which is leading to lot of inconsistencies. For example, assume the user changed the country from IN to the US in the app. And from the Firebase dashboard, we send push notification targeting Indian users, the push notification will also be received by the above user, which is not correct.
To solve this problem we came up with 2 solutions,
Create a new custom user property called app_selected_country. This is a great solution, but we can't use this property immediately because of old & existing users won't be having this value without they update and use the app.
If we can change the automatically logged user property programmatically from the app and website, we could update the country user property to the app's country.
Our preferred option is the 2nd one. Because we'll be able to use the country user property the same as before. Even if the users won't update the app, we'll be able to use this property with existing data errors, which is fine for us.
The challenge with this approach is that we can't find any documentation regarding updating automatically logged user property.
So can you please help me answer these questions,
Is it possible to update automatically logged user property in Firebase? If so what is the user property key for the country?
Is there any side effect of doing this? We are a bit worried because we are changing the value detected by Firebase.
Unfortunately there is no way to change the auto-detected country. You will need to use your first proposed solution.
My app presents the device contact list for the user to select a contact. However, I do not see the device login - the name & email used to sign in to the android store - in the contact list.
I've read other posts showing how I can get the device login from the system profile. However, I'm trying to understand what prevents or allows that login info from getting added to the gmail account contacts list.
Ultimately, I want to use this info for the user to register his usage of my app. With that, I intend to receive the user's name and email address (with his permission, of course). Perhaps there's a better way to approach what I want.
That account used to login to the device is the user's account. The contact list you are talking about are the user's contacts. If I were the user, I think it would be odd to have myself listed as one of my contacts...
It sounds like you already know how to get the information you want. I don't believe there's a "better" approach than simply doing that. You need to be more clear on why that is not a good approach or what about that approach needs to be improved.
I think this may not be the right question for this forum, but I could not think of where else to post it.
However, here goes. I am creating a dating app in android. One of the major hurdles I am facing is user authentication and verification.
Put simply, how do I ensure that a user is who he/she really says he is? How do I prevent, or reduce people creating fake profiles on the app? One way to do this would be to force the user to connect with his facebook account, but again, fake facebook profiles can be created.
Is there any other good method to ensure user verification?
The best way I can think of, although not fool proof, would be when the user creates an account it sends them an email where they need to click a link. Clicking the link can ask for some confirmation of something, such as their chosen username and or the first name and last name etc. If they fill in this information from the email, they're probably legit and you can mark the account as active within the database. If after x number of days delete any accounts that have not been verified.