After Portal's authentication is completed, the user sees what pages, what operations can be done, how long can you stay?——These details are overlooked in many projects. The integrated firm usually focuses on whether the authentication is going to pass, and the experience after certification belongs to the community."Follow-up optimization"In the range, it drags long after the line. But in practice, the post-certification user experience has a very significant impact on overall network satisfaction.
The most common design error is that the user was left without any hint after certification, and did not know that it had been connected to the Internet or what should be done. Some people consciously refreshed their browsers to see if the pages were changing, and some even didn’t know they would manually return to the site they wanted to visit. This was not apparent when small-scale tests were conducted, but when large scale rollouts were made, user confusion led to a huge amount of ineffective technical support worksheets.
The design of the authentication successful page has several points. First, you have to clearly inform users that the certification is complete, for example."You have successfully connected to the Wireless Network. Welcome to". The second is to give the operational entry back to the previous page, which is viewed before user authentication and should be able to return with one key when authentication is successful. Third, if there are usage limits or traffic restrictions, you must make clear here that it does not wait until half of the user is forced down.
The second common error is Portal's time-limited control and active alarm mechanism. Many Portal systems default to set fixed duration authentication, for example, eight hours per authentication, but the user does not know how much time it has left and is about to expire without any warning. As a result, users suddenly break out of their network between meetings or midway video calls, with very poor experience. Better to show the maturity of this authentication on Portal pages, while popping up an alert page 15 minutes before expiry so that the user can choose whether to continue.
The third problem is Portal's exit mechanism. Users should, in theory, either write off their authentication and release their session resources when they leave the company or no longer use the network. But few do so, with the result that users are hanging up and consuming system resources without saying that there are security risks if equipment is lost or used by others. It would be better for Portal to support active cancellation entry, which allows users to access Portal write-off page closing sessions at any time.
Another kind of experience problem comes from the suitability of Portal pages. It is important to have mobile devices in the mainstream and Portal pages open on a cell phone. Many companies ' Portal pages are designed on an early basis based on PC browsers, displaying inappropriate scales, too small buttons and changing input frames on their phones, which do not affect authentication functions but significantly affect user experiences.
In summary, Portal certification should be designed to include at least clear identification success tips and returns, clear time-to-time displays and renewal mechanisms, active write-off entry and passive overtime release, and a matchability test for the end of a cell phone. The details are good Portal and poor Portal, with very marked differences in user perceptions.