There are basically two ways to implement HTTPS in Android:
One is to not verify the certificate, one is to have a certificate of authentication (prevention of phishing). The second approach is more complex and requires the conversion of a CER certificate into a BKS type. This way can also only be simple to prevent fishing, not effective to prevent fishing. Prevent fishing ultimately by user identification, download the application in the formal channel. The application certificate can also be used to verify the function of the client, personally think that using the certificate to verify the client is inappropriate, if you use the certificate authentication client, the certificate must be stored in the application or download, the Android app is an apk file, it is easy to get inside the file, if it is the way to download, Easier to get through. If you want to authenticate the client, you personally think that using so files to encapsulate the data is better.
Our mobile phone often use public WiFi, when our data is a burst, this is the transmission is very dangerous, the user's privacy data is easily accessible to third parties, the use of HTTPS in the Android client can effectively prevent data leakage, prevent third parties to intercept the application of communication data.
http://blog.csdn.net/xyz_lmn/article/details/8027334
http://blog.csdn.net/xyz_lmn/article/details/6312827
http://www.guokr.com/post/114121/
http://my.oschina.net/blackylin/blog/144136
Http://developer.android.com/training/articles/security-ssl.html
Http://developer.android.com/training/articles/security-tips.html#Networking
Usage of HTTPS