When to Use Lock vs. Custom User Interface

Last Updated: Sep 27, 2024

Overview

This article explains when admins should choose Auth0 Lock or a Custom Interface.

Applies To

  • Auth0 Lock
  • Customized Universal Login

Solution

Lock is a drop-in authentication widget that provides a standard set of behaviors and a customizable user interface.

Auth0 SDKs are client-side libraries that do not come with a user interface but allow for expanded customization of the behavior and appearance of the login page.

The Authentication API provides integration without requiring the use of Auth0 SDKs and Lock. Especially recommended to those who want to build their user interface themselves.

The best option to choose will depend on the needs of the app. Please reference our documentation on this subject for a more detailed explanation.

When to use Lock

Consider using Lock for:

  • A quicker and easier implementation of Auth0 and a ready-made responsive UI.
  • The structure, look and feel of Lock
  • An application that includes many of the use cases that Lock handles out of the box:
    • Enterprise logins
    • Databases with password policies
    • User signup and password reset
    • Authentication using social providers
    • Avatars

When to use Custom User Interface

Consider implementing a custom user interface in conjunction with an Auth0 library or the Authentication API if the application:

  • Has strict requirements for the appearance of the user interface.
  • Has strict requirements for file sizes - the Auth0 libraries are significantly smaller than Lock, and dealing with the API directly would not require any additional weight.
  • Needs a completely customized HTML, CSS, and JavaScript.
  • Only username/password and social provider authentication are required.
  • Multiple databases or Active Directory Connections are required.

Related References