Hi, You can use SharedPreferences as Frank mentioned. In client: When your first activity runs (or may be you can override Application and put it in the constructor): Check in SharedPreferences whether the registration information exists or not. If exists, then do not send request to server. If does not exist, then get name/email (may be through a activity?) and send request to your server. When response is got from server, save registration information in SharedPreferences
In server: When a request is received, check in database whether the email is already registered or not. If not registered, then put the record in database. If registered, then do not put in database (uninstall-reinstall check) Finally, did you really mean "if the user has registered with that cellphone" ? What if the user wants to use the app with same email on different devices? If you really want to identify in device level (rather than email level), then you may want to send and also save in DB the ANDROID_ID of the device. http://developer.android.com/reference/android/provider/Settings.Secure.html#ANDROID_ID Regards Sarwar Erfan On Aug 18, 4:16 am, Frank Weiss <[email protected]> wrote: > I'd use SharedPreferences for that. You will also need to add a use > case for the user uninstalling and then reinstalling the app. In that > case, SharedPreferences would be empty, but your server DB would have > a record of the prior registration. -- 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
