Consolidate token onboarding/phone verification processes
Goal
There's significant duplication in phone verification and token onboarding flows/components
We have:
-
m-phone-input
+m-phone-input--country
, used inm-juryduty__session
. -
m-phoneInput
+m-phoneInput__country
used in onboarding's "verify uniqueness" step (m-onboardingV3__phone
) and also in wallet > join rewards >m-token--onboarding--rewards
-
m-juryduty__session
also uses a very oldm-token--onboarding--rewards
process.
What needs to be done
-
Compile/take screenshots of all of the phone/token onboarding steps used in onboarding (v3), jury duty and wallet -
Analyze the overlaps and gaps between them -
See how we can consolidate these to reduce duplication -- choose a winner and use it everywhere
QA
Complete different onboarding processes
UX/Design
Not needed, but might be needed depending on findings
Personas
Developers, new users
Experiments
N/A
Acceptance Criteria
-
Use one token onboarding process only -
Use one phone verification component only -
Delete obsolete files
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments
Edited by Olivia Madrid