Completed
Visibility of system status
Class Central Classrooms beta
YouTube playlists curated by Class Central.
Classroom Contents
Building an Auth Experience for Humans - Best Practices and User-Friendly Design
Automatically move to the next video in the Classroom when playback concludes
- 1 Building an Auth Experience for Humans
- 2 This is for making auth SUCK LESS.
- 3 15 Rules for User Sign In
- 4 Apply inline validation for the email field
- 5 Reset password should carry the email into the new form
- 6 Offer password reset on the third try
- 7 Send a password reset link
- 8 Allow password managers to capture the user login credentials
- 9 On mobile apps, allow users to use their on-device authentication to login
- 10 Single Sign On (SSO) as a login option
- 11 Two-step authentication should be a norm for sites that contain sensitive information
- 12 Understand user's cognitive load for deeper navigation and design'outs' for errors
- 13 Persistent login should be the norm for non-sensitive sites
- 14 Don't force the user to login if, without login, the user can complete the journey
- 15 Upon login, if the user has items from a previous session, OVERWRITE IT!
- 16 Prompt account creation after the primary journey has been completed
- 17 Status links should not ask for logins (i.e. orders)
- 18 Abandoned Carts links should not prompt for login
- 19 Visibility of system status
- 20 Match between system and the real world
- 21 User control and freedom
- 22 Consistency and standards
- 23 Error prevention
- 24 Recognition rather than recall
- 25 Flexibility and efficiency of use
- 26 Aesthetic and minimalist design
- 27 diagnose, and recover from
- 28 Help and documentation
- 29 Cloud Identity is the house and the doorframe. You design the door.
- 30 Don't wait for a designer to take care of your users.
