Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GoodID-dapp]: Segmentation implementation #552

Open
6 tasks
L03TJ3 opened this issue Apr 23, 2024 · 0 comments
Open
6 tasks

[GoodID-dapp]: Segmentation implementation #552

L03TJ3 opened this issue Apr 23, 2024 · 0 comments

Comments

@L03TJ3
Copy link
Collaborator

L03TJ3 commented Apr 23, 2024

Business Description

Segmentation Flow

Detailed Description of Functionality

full description can be found in the business description

  • Load/Show segmentationController based on verified param
  • Load/Show SegmentationDisputeController when someone clicks on 'this is not me' on the segmentation screen
  • Load the checkAvailableOffers component when a user clicks on 'next' on the final Segmentation screen

Technical Implementation

  • Add the SegmentationController to the GoodID page
  • Add the SegmentationDisputeController to the GoodID page
  • Load SegmentationController on the good-id page based on the verified param
  • It should navigate to the claim page if someone is not eligible for any offers
  • Make sure first-time claim flow (based on verified param) is passed down correctly

Design Reference

figma:https://www.figma.com/file/ihw1PxBvLxacTHnN2aj4lC/3.-Product?type=design&node-id=14739-101891&mode=design&t=HVwiPE3o3n06ixlS-4

(Preview-Desktop: HappyPath)
image

(Preview-Mobile: HappyPath)
image

Acceptance Criteria

Specify criteria that will be used to determine if the feature meets the requirements and functions correctly.

  • (Should include a list of testing points for QA how to verify design/functionality)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant