Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better device id without privacy issue #15

Open
xcv58 opened this issue Oct 5, 2015 · 2 comments
Open

Better device id without privacy issue #15

xcv58 opened this issue Oct 5, 2015 · 2 comments
Assignees

Comments

@xcv58
Copy link
Member

xcv58 commented Oct 5, 2015

No description provided.

@xcv58 xcv58 self-assigned this Oct 5, 2015
@xcv58
Copy link
Member Author

xcv58 commented Oct 5, 2015

According to http://android-developers.blogspot.com/2011/03/identifying-app-installations.html

The ANDROID_ID may be the best choice.

From http://android-developers.blogspot.com/2015/05/a-closer-look-at-google-play-services-75.html
Instance ID seems better because it ties each app.

But here we got a new issue. If two apps use Maybe Library in one phone. The Instance ID may override each other.

Probably a better way is put gcmid to device->package->gcmid instead of current implementation: device->gcmid.

That means: in backend, we have deviceid means a real Android device or a profile on Android deivce.
That deviceid may have multiple gcmid.

@xcv58
Copy link
Member Author

xcv58 commented Oct 5, 2015

According to https://developers.google.com/instance-id/reference/

The Instance ID API lets you integrate Instance ID with your Android or iOS app. Instance ID provides a unique identifier for each instance of your app and a mechanism to authenticate and authorize actions, like sending messages via Google Cloud Message (GCM). The InstanceID is long lived, but may expire for the following reasons:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant