-
-
Notifications
You must be signed in to change notification settings - Fork 158
Open
Labels
Ready for DevelopmentAutomatically assigned to issues that are ready to be picked upAutomatically assigned to issues that are ready to be picked upfrontendFrontend developmentFrontend development
Description
Summary
Now that we have a back-end for Phone Number Verification hooked up, we're ready to introduce the real user-facing side of this (behind a flag). This flow is documented in the linked Figma, but includes: Adding a "Verify Phone" box to the Edit Profile page (when verification is needed) and adding CTAs leading to the Edit Profile page flow at the start of the Submit Testimony flows,
Success Criteria
- Edit Profile Page has a "Verify Phone" section (as a card in the "Verify Account" section).
- Both of those sections only appear when a user still needs to verify their account
- Add a CTA banner to the Home Page prompting users to verify
- This can likely use the new
AnnouncementBannercomponent
- This can likely use the new
- Add a CTA to the Submit Testimony flow
- This needs to handle three cases:
- The Submit Testimony box from the Bill Details page (e.g.
https://maple-dev.vercel.app/bills/194/H5000) - The actual "Submit Testimony" page itself (if a user is linked there directly) (e.g.
https://maple-dev.vercel.app/submit-testimony?billId=H5000&court=194&step=position) - The "Add Testimony for H.123" button from the Testimony Details page (e.g.
https://maple-dev.vercel.app/testimony/JEzCsV1OiC9hwCyrcON5A/1)- This doesn't have the same CTAs the Bill Details page has - we should either tweak the UX here or (more simply) - just point the user to the Submit Testimony page and let that CTA handle this case.
- The Submit Testimony box from the Bill Details page (e.g.
- This needs to handle three cases:
- Document the best way to test this flow (e.g. do we use a dummy phone number that can be used for testing? a good way to reset a valid phone number for re-syncing to the same account or other accounts? Is there a Firebase-idiomatic way to handle testing this?) - can be as simple as a note on the Github Wiki / README we can point to, but we should have a way to be confident we don't break this flow with future changes, even if just through manual testing for now.
Additional Links
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Ready for DevelopmentAutomatically assigned to issues that are ready to be picked upAutomatically assigned to issues that are ready to be picked upfrontendFrontend developmentFrontend development