Web: Refactor onboarding modal
Goal
The current onboarding flow is a series of individual modals daisy-chained together. This may result in awkward behavior of modals closing an opening in succession.
Refactoring this to a single modal can deliver a smoother user experience.
What needs to be done
Ben suggested refactoring the processing into a single modal that advances without closing / opening, perhaps with consistent placement of continue / skip buttons.
QA
Gherkin: Gherkin tests are addressed here: front#6030 (closed)
UX/Design
Winning design from user testing - https://illuminate-multiply-001079.framer.app/webFinal https://illuminate-multiply-001079.framer.app/mobFinal
Mobile web screenshot
Web screenshot
Mobile
-
Is Mobile Required?
Personas
The new user!
For seeing research and insights, check out this link. UX Research
Experiments
Deploy as an A-B experiment in Growthbook against the current onboarding modal daisy chain.
We'll compare on the basis of:
- Signup completion
- Email verification completion
No significant change is expected.
Acceptance Criteria
-
New onboarding components created, being controlled via Strapi -
Backend state storage and retrieval -
CTA's should load the onboarding via the modal, homepage/register/login will be full page design
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments