Login: with Phone Number #71
Description
Images Link to Figma here.
### **A user wants to login with their cell phone**
- [ ] Create Login with Cell phone button
- [ ] Create Login with Cell phone button
- [ ] This loads the Log in with Cell phone screen
- [ ] Screen has a link to “log in using different method that goes back to choices screen
- [ ] Type in your phone number
- [ ] IF the phone number is not valid, show the “Error Message”
- [ ] If the phone number is valid, text a security code to the phone
### **When a number is typed in and clicked Login**
- [ ] If >+1 user with matching dnis is found (at least 1 of the usrs ha validated the dnis associated with their account), then whow the pin entry screen
- [ ] IF the usr has more than one account, return a drop down box of accounts to select from
- [ ] Use the account drop down box to inform the submit button where to send the user next
- [ ] If the user only has one account, do NOT show the drop down box
- [ ] Provide a resend button that will repeat the code sending operation
- [ ] make sure the cancel button will return you to the previous screen
### **Type in Security Code**
- [ ] if 5 digit code does not match, show error message
- [ ] if 5 digit code matches, send email to the email address on file notifying user of the login
- [ ] route to Menu Page of app
Potential issues to address via Braden:
🤔 Also another potential issue here for existing users who have added phone numbers already (and wont be validated).
I think in this case we should just provide you with an error. "The associated account has not verified this phone number. Please login using credentials and request a verification token."
This list must consist of only the subset of associated users that are also validated. Since validating phone number is a new concept for existing users (meaning they would likely have to make an effort to go do it), maybe we need to show accounts that have not been validated as greyed out or something? Would probably need a note to go along with it somehow.
Also -- another api change here is likely for the existing registration flow. If you give us a phone number initially, we should probably go ahead and send you a validation text (like we do email)