Skip to main content

Login form authentications

We have been using login forms from many many years now. As the web is continuously evolving these form have gone through many unnoticed changes over all these years.

There was the first era of showing fields like username, password, remember me, forgot password, need help, reset, and an anonymous question mark which was too much to think about and proceed with the login process.

Gradually, these forms have become shorter and shorter with only username and password fields because that's what the user is actually interested in using as interaction elements to accomplish the task.  

The validation process:
Ever since beginning websites do validate both the username and password fields, but there are another type validation requirements; such as, for security reasons some websites don't validate usernames; the login process is only completed after typing a correct password.

In such cases we face some common questions like:
1. Should I use the current trend of showing username on first screen and password on second screen?

2. What will happen if the authentication fails on second screen?

3. Should we redirect the user to first screen with a message 'your username or password is incorrect'?

4. Or should we use the traditional username and password fields on same screen and then so the failure message, and if we do which field should have a focus?

A lot to think on....

The best bet here would be to use the traditional login form with username and password fields placed on same page with a forgot credentials link in case if the user doesn't remember his credentials (username and password both), and a signup link for new users.

What about the focus?

Well, when you are not validating the username field there is no point in keeping the typed username in the field after validation error as there is a possibility that the username also could be wrong. So it's best the system resets the form entirely with a focus on username field.



Comments

Popular posts from this blog

Mobile app notifications for business meetings

Annoying notification is one of the top reasons why people uninstall mobile apps, so the notification designers have to be very careful while designing their behavior. At first the app should ask users as to when they would like to be reminded about the meetings, because the user behavior  vary; some people might want to be reminded a day before and also 30 minutes before the meeting starts as they might have to prepare for the meeting; and some people might be just ready to jump into the meeting without any delay so they would want to set the reminder to 5 minutes. So, let the user set time to receive a notification. Once the notification is on screen; the user should be able to dismiss it or open the meetings app - this feature can be used with the slide option. In case if the user doesn't attend the meeting and the meeting time is over, then the notification should still sit on screen but in negative state to let the user know that he/she has missed it. And there shou...

Questions for Usability Testing

Layout design  What is your first impression of this design/layout? What do you notice first when you look at this screen/page? Did you have any trouble understanding the interface? Design clarity  How would you rate the clarity of the instructions/guidance provided? Do the options/buttons/links make sense to you? Are there any terms or language used that are unclear? Were there any elements on the screen that distracted you or seemed unnecessary? Design look and feel  How did using this product make you feel? Were there any moments of frustration or delight while using this product? How does the overall aesthetic appeal to you? How would you describe the tone and language used in the product? How would you describe the overall look and feel of the interface? Does anything stand out to you immediately as either positive or negative? Findability and navigation experience  Were you able to find all the necessary information to complete this task? How easy or difficult ...

Design Proposal: A Comprehensive Banking Payments App

Understanding the User and Business Goals User Goals: Convenience: Easy access to accounts and seamless transaction processing. Security: Robust security measures to protect financial information. Insights: Clear financial overview and personalized insights. Support: Reliable customer support channels. Business Goals: Customer Acquisition: Attract new customers and increase market share. Customer Retention: Improve customer satisfaction and loyalty. Revenue Generation: Increase transaction volume and fee income. Operational Efficiency: Streamline processes and reduce costs. UX Design Principles Simplicity: Clean, intuitive interface with minimal clutter. Clear and concise navigation. Easy-to-understand information hierarchy. Security: Strong authentication methods (biometrics, PIN, OTP). Secure data encryption and transmission. Regular security updates and vulnerability assessments. Personalization: Tailored user experience based on preferences and...