A useless function

Today, make a new feature, feel this feature is a superfluous thing.

Background:

1. This product is b/s architecture, IE browser/server architecture.

2. This product is divided into several module pages. Administrators can define user access to different modules, that is, the same user can access only the specified modules based on his or her permissions, and the same module, which can only be accessed by those users with the specified permissions.

This is the new feature.

In a module, click the "Exit" button –> to the login page –> then login to enter the page –> into the module (the original is to enter the first page)

The reason this feature is redundant is that

The user clicks the "Exit" button to reproduce the scene:

1. Safely exit the system. In fact, when we exit the system, in addition to the bank and other systems, there are several people click the Exit button, are directly off the page! And when these click the Exit button to exit the user, there are several times logged out immediately after login?

2. Switch users. After I log in to the product with "user1", I switch to the "user2" login product. But at this time, User1 's Operation page has nothing to do with User2.

In the scenario above, "scenario 1" may have this feature demand, but the number of such requirements is very small (and most users do not click the Exit button at all), and "Scene 2", there is no need for this feature. So it feels like an extra feature.

And what I can't understand later is that the company's requirements for this feature are so rough.

1. Implementation, only require re-login into the page is the last logout operation of the module page, and did not do user identification. This leads to the situation, if we switch the user (user1 switch to User2), User2 will also be user1 the last operation of the page, more frightening, user2 if there is no permissions for this module, will go to the error page, and this error page, No entrance to the homepage!

In the development of products, a variety of feature, we need to determine whether this feature will be used. If this feature is hidden in the nook and cranny, do we still need to do it, does its priority need to be adjusted? If we do it, should we try to do it well, at least to make the "user experience" better than without it?

A useless function