Sounds like we are dealing with exactly the same problem Tom. I was considering a solution similar to yours, but I wasn't going to force a password - I really hate being forced into creating a new account wherever I go. The sooner the world gives over to ubiquitous OpenId the better.
I was planning on either using the IMEI or a randomly generated number (or a combo of both) as the unique identifier. And I only want a display name from the user, to show alongside their scores. That way I don't force them into creating an account. The struggle is determining what value I can use for the unique identifier that will allow the data to follow the user as the upgrade their device. Tom,. when a user installs your app a new device, how do you plan on linking their new anonymous account with their existing account? On Oct 13, 9:14 am, Tom Gibara <[email protected]> wrote: > I've been wrestling with the same problem. > > I've decided that my approach will be to register, unseen to the user, an > anonymous account when they first need an identity on the server (eg. when > posting their first high-score). Then, after they have continued to use the > app for a time (eg. when they have posted a certain number of scores) they > will be invited to associate credentials with the account (in my case a > username and password) with text that explains the benefits (ie. they can > carry that identity over to other devices and between other applications I > write). > > My aim is to avoid pestering users who are just trying-out the app without > letting active users miss out on the benefits of registration > (or penalizing them for delaying their registration since everything they > have done with the app prior to that will remain associated with the same > account). > > A background server task will periodically wipe abandoned anonymous > accounts. It's definitely more work work this way, but I think it's > favourable to the users. I'd be interested to know if anyone else has found > a good solution that's less work. > > Tom. > > On 12 October 2010 22:55, William Ferguson > <[email protected]>wrote: > > > I'm looking for a way to determine user identity so I can globally > > track game scores off phone. > > > IMEI provides identity of the phone - not effective if phone is on- > > traded or upgraded by individual. > > USIM provides identity of phone carrier subscriber - assumes device is > > phone, and currently has a SIM card > > > I'd like to be able to provide continuity as a user upgrades to a new > > device. > > And I dislike being forced to create an account on each global scoring > > system, so I don't want to force that on my users. And my end user > > experience with OpenFeint leaves me disinclined to use it. > > > It doesn't need to be bullet proof. But it does need to be hassle free > > for my users. > > > Is there any other identifier on an Android device that I can use to > > link data more cleanly with the current owner? > > And how would I get hold of that identifier? > > I'm thinking something like the user's Google account .. or similar > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected]<android-developers%[email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
