It sounds to me like you're approaching this a bit backwards. Rather than asking what information should go on a registration form -- you should be looking to only collect what information you need.
For example: do you really need to collect the phone number to provide your service? Phone numbers are seldom good ways to communicate with customers, and are seldom needed to provide mobile services. An email address, on the other can provide value, in allowing a user to reset their password semi-securely, and allows you to contact them with information about updates. Generally, the rule should be -- if you don't need it, don't collect it. If you do collect it -- protect it. That means, among other things -- store it encrypted. Also, if you collect information for marketing purposes, limit it to what's actually useful, make it optional, and try to provide value to the user as a result. If it's for statistical purposes, consider collecting it separately, without any personally-identifiable information. This approach will help you keep on the right side of the various national data privacy laws. It's probably not enough -- at a minimum, you'll also need to consider disclosure, retention policies, etc. Any time you collect data from users, you need to give the matter some serious thought. My final suggestion is: Do not collect this information directly in your app, and then send it to the web service. Instead, send them to a web page using a WebView, and collect it off of the device using an HTML form, via the https: protocol (for privacy). The big advantage here is you can update your form, without releasing a new version of your app, and without concern with different versions of your app being out there (which will happen, at least for a while). You can include your app's version number in the URL you send. Then, if you need some of the information on the device as well, or if you need additional information from the server (perhaps, say, an authentication token), you can add a Javascript handler via WebView.addJavascriptInterface, and use that to communicate information back from your web server to your application. On Dec 1, 2:13 pm, "[email protected]" <[email protected]> wrote: > Hi, > I am new to Phone app programming. I am starting with Android. > What is typical registration page for a typical app. I am thinking > of: > 1. Phone Unique Id > 2. Phone number > 3. User name > > When a user downloads my app I need to collect all of the above and > call a web service to save this info. > This info will be used to provide other services. > > Can I get some codes sample and/or pointers. > > Thanks in advance, > Nagaraj -- 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
