The Hidden Costs of Using Username and Password for Authentication

This is a critique of what has historically been taught in UX about giving users the option to choose how to log in to a website or app.

UX teachings often focus on giving users multiple login options, but in practice, this can complicate development and increase costs for MVPs.

We all love designing username and password screens, feeling productive and like valuable members of society, but the reality is that these views increase design and development costs and add long-term maintenance.

If you’re developing an MVP, instead of creating multiple screens like:

Login, Register, Lost Password, Change Password, Send Code, Insert Code* + Modals + Form errors + Toast notifications + Send more emails.

All you really need is one screen with a message, an image, and two or three buttons: Sign in with Google, Sign in with Facebook, Sign in with Apple.

In both cases, you’ll still need to implement OAuth and Email/Password.

OAuth alone is just one screen and can be implemented in a couple of hours.

Keep it simple. For MVPs, one screen with OAuth can save hours of development, reduce maintenance, and improve the user experience.