Please enable JavaScript.
Coggle requires JavaScript to display documents.
Existing, Email Only, Phone & Pswrd Only #, Hybrid Approach, User Name…
-
-
-
-
-
-
-
-
Actual Interactive Steps: 7-8
Cognitive Load: High
General Perception/Feeling: Doubted, frustrated
Potential Logical Errors: Multiple
Complexity:
Time-to-value:
Mobility/Flexibility:
User profiling:
Compliance:
Web3 Enablement:
Security:
Estimated completion time
Actual Interactive Steps: 3-4
Cognitive Load: Medium
General Perception/Feeling: Happy, Excited
Potential Logical Errors: Dual unclaimed accounts with same phone error
Actual Interactive Steps: 3
Cognitive Load: Low
General Perception/Feeling: Happy, Excited
Potential Logical Errors: Almost none
Actual Interactive Steps: 2-3
Cognitive Load: Very Low
General Perception/Feeling: Good, but not satisfied
Potential Logical Errors: Account conflicts, unclaimed accounts, multiple accounts
Actual Interactive Steps: 3-4
Cognitive Load: Medium
General Perception/Feeling: Non secure, doubted, frustrated with usernames
Potential Logical Errors: Multiple levels of errors
If a manually-provided optional email is used to log in with SSO:
If the email is validated: ->
Validate phone -> Login
If the email is not validated:
This account is non-accessible through SSO, please provide credentials to proceed. [LOGIN]
If Login Mechanism is Email or Phone:
If an account was originally created with SSO email and validated Phone
user tries to login with by typing that SSO Email in the field (instead of Phone):
With any password (since the password wasn't originally created)
• Account does not exist.
• Incorrect credentials - try again with Email/Phone or continue with Google
-
If an account was originally created with SSO email and user tries to login with by typing that SSO Email in the field:
With any password (since the password wasn't originally created)
• Account does not exist.
• Incorrect credentials - try again with Email/Phone or continue with Google
If SSO only facilities Gmail links, then manual credentials such as Yahoo couldn't be used for the SSO or recovery route.
-
-
-