[GoodID]: Onboarding flow implementation

[L03TJ3]

Business Description

We want to implement a new onboarding flow.

Detailed Description of Functionality

When a user clicks on the claim button in the dashboard the following things could happen:

Scenario: Not whitelisted (new user)

• if not whitelisted the user will be navigated to the face-verification flow

Scenario: Whitelisted

• If an existing identity certificate can be found in the local storage, the user will continue to the claim screen
• if there is no identity certificate stored we verify when was the last time they did the face verification. if this was after the launch date of the new good-id flow, the user continues to the claim screen
• if there is no identity certificate and the last face-verification was before the launch date of the new good-id flow, the user continues to the face-verification flow

Flow for the new fv-intro screen: What should happen when a user clicks on 'I Accept, Verify Me' Scenario: new user or expiry date is > 3 months

• user navigates to the start of the face verification

Scenario: user is whitelisted but the expiry date of its current fv registration < 3 months

• user navigates to the segmentation screen

Technical Implementation

• [x] change the logic of the claim button to navigate to the new claim screen or the new face-verification intro-screen
• [x] Replace the current IntroScreen of the face-verification with the new onboard screen
• [x] use the wallets screenprops.navigateTo (see code for example usages) to send a user (after clicking on 'I Accept, verify me') to either segmentation or to the start of the face-verification. this callback will be passed down to the onboard screen
• [ ] should pass down fullanme to the intro-screen if user has set one. Name can be found in the profile. to fetch the profile you can use this hook. it returns an object 'profile'. the name can be found in profile.fullName

Design reference

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) filled out by the development team or can contain suggestions._