Login UX Patterns

Key Design Considerations

• Email-first login — Ask for email first, then determine the auth method (password, SSO, magic link). This avoids forcing users to remember which method they used.
• Don't split sign-up and sign-in — A single entry point that handles both reduces friction.
• Show password option — Let users toggle password visibility to reduce errors.
• Magic links — Passwordless login via email link. Simple but adds email dependency.
• Social login — Reduces friction but creates provider dependency.

The "Which Method Did I Use?" Problem

Jason Fried has noted the frustration of login pages that force you to choose between password, Google, SSO, etc. — when you can't remember which one you originally used. The email-first pattern solves this by detecting the auth method server-side.

Best Practices

• Default to email-first flow
• Support password managers (proper form markup, no custom inputs)
• Provide clear error messages (but don't reveal if an account exists)
• Remember the user's preferred method for return visits