Many people are used to having to create a username to access a website. But let's be honest: in most cases, this is an unnecessary headache for both the user and the developer. It's time to admit that requiring a login is outdated.
In many content management systems (CMS), the "Login" field is enabled by default. Developers simply leave it in because "that's the way it's historically been." But just because a method is old doesn't mean it's convenient. More often than not, it's simply unnecessary.
It's easier and more accurate to use an email address for authorization. Here's why:
- It's impossible to forget. Everyone remembers their email address, but a made-up login like "kotik1992" can easily be forgotten in a week.
- It's always unique. No two people have the same email address. And you have to try out logins: "Vasya," "Vasya1," "Vasya_123."
- Fewer fields means easier registration. The less information a person has to fill out, the higher the chance they'll complete registration and stay on the site.
So, by forcing them to create a username, we're forcing the user to remember unnecessary information and waste time choosing a username. And they already have an email address.
There are rare exceptions when a username is essential. Let's look at them:
1. Public Page (Profile)
If the user has their own visible page on the site, for example: site.com/users/vasya_petrov. In this case, the page address should be clear and understandable. Showing an email address ([email protected]) in the link is unsightly and unsafe.
2. Messengers and Online Games
Where people find each other for chat or games. A nickname (pseudonym) is part of self-expression. In a chat or game, a username serves as a name, not a technical key for entry.
We've decided to move away from outdated rules. In our system, login is disabled by default.
You don't have to worry about removing this field from your code. Users simply register with their email address and log in using the same email address.
But if you absolutely need a login (for example, if you're migrating an old site to our CMS and don't want users to have to retrain themselves), we've left the option. Login can be enabled in the settings with a single checkbox.
