Zhaotong java Training School tells you the significance of adding verification code function in web design?

In the prevailing environment of ticketing software, the appearance of verification code can greatly reduce the occurrence of these software accessing websites and malicious registration, but sometimes too strict verification code design will also hurt users. Let's think about the significance of verification code function design.

Thinking 1: Don't put the blame on users.

I don't know if it has ever occurred to you that letting users identify and input distorted verification codes is actually because the service provider has no ability to silently distinguish between people and machines, and the operation of inputting verification codes is actually of no value to users.

Once I got a call from a user complaining that I couldn't handle the verification code. I explained to him that we were attacked, so I temporarily raised the level of the verification code. After the phone call, I habitually apologized to him, but the user comforted me very considerate and said that there was no need to apologize. After all, being attacked is not our fault.

At that time, my heart was hot and my face was red. He's right. It's really not our fault to be attacked, but it's not the user's fault either. Let them pay the cost and take the time to tell whether the circle in the picture is O, 0 or 6. In fact, let them bear our responsibilities.

In other words, if we think more radically, there are still many designs in our software services that shirk responsibility, such as allowing users to compare prices among thousands of goods, such as various complicated interface parameter settings and interest choices. If you think more broadly, it seems that all bank account passwords are unnecessary, and so is the queue in the supermarket.

Wouldn't it be better if users can enjoy the same quality service without paying the cost of screening and price comparison, or without spending energy to remember account passwords?

Based on this thinking, should we immediately get rid of these shirking designs, such as thinking of a more complicated scheme to replace the existing verification code mechanism?

These are two thoughts about verification code.

Thinking 2: Balance of Scheme Selection

An effective design is not necessarily a good design. For example, I used to design products with verification codes. At some special stages (like the targeted attacks just mentioned), we will upgrade the verification code mechanism to make verification codes appear more frequently and more difficult to identify, so as to resist the targeted attacks of some key entrances.

This strategy is effective, but it does great harm to users. After the upgrade of the verification code mechanism, the time spent in the user login process will obviously increase, and the pass rate will also decrease, and there will be a large number of user complaints at once.

However, from the perspective of service providers, the problems faced at that time were quickly solved with low cost. Computer training/think that this is the "balance" that has to be made in the process of product design scheme selection. Many times we can't implement a perfect solution for users at one time, so we need to find a subtle dynamic balance between product interests and user interests.