Code-based email verifications in mobile app
Goal
Implement code-based email verifications in the mobile app and make the verification part of the initial onboarding flow, before a user reaches the Newsfeed.
What needs to be done
- Implement code-based email verification flow to the mobile app new user onboarding.
QA
UX/Design
Screenshot for quick reference, see Figma mocks for latest spec.
Personas
- New users
Experiments
Code-based verification should be tested versus existing link-based email verification, measuring for % of signups that result in email verification.
Acceptance Criteria
-
Given a user is creating a new account in the app, and the user has already filled out the fields on Join Minds
screen, and all fields are valid, when the user clicks the blueJoin Minds
button, then a code-based verification email is sent to the user's email address, and the user is navigated to the code-basedVerify Account
screen. -
When the user is navigated to the code-based Verify Account
screen, then the user's cursor is automatically positioned in theVerification code
text field, and the keyboard defaults a numeric layout. -
Given the user is on the code-based Verify Account
screen, and the user inputs an invalid code, when the user tapsVerify
button, then the "Invalid code" error is displayed adjacent to the code field. -
Given the user is on the code-based Verify Account
screen, and the user inputs a VALID code, when the user tapsVerify
button, then the email address is verified and the user is navigated to the Newsfeed.
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments