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]: onboarding flow implementation #550

Open
4 of 5 tasks
L03TJ3 opened this issue Apr 9, 2024 · 0 comments
Open
4 of 5 tasks

[GoodId-dapp]: onboarding flow implementation #550

L03TJ3 opened this issue Apr 9, 2024 · 0 comments
Assignees

Comments

@L03TJ3
Copy link
Collaborator

L03TJ3 commented Apr 9, 2024

Business Description

We want to implement a new onboard flow

Detailed Description of Functionality

Claim page

the claim page has two different states:

  • wallet is not connected: the blue claim button shows and by clicking on it a onConnect callback should handle the wallet-connection
  • wallet is connected:
  1. it checks if someone is whitelisted
  2. if not whitelisted, onUpgrade callback should handle navigation a user to the /goodid page (for onboard flow)
  3. if whitelisted, the claim-flow will be shown
    a. newsfeed provider is already added

GoodId page (Tab for this page is only shown for already whitelisted wallets, that will not change)

The goodid page can have various states.

Technical Implementation

Design Reference:

(Mobile)
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)
@L03TJ3 L03TJ3 changed the title [GoodId]: onboarding flow implementation [GoodId-dapp]: onboarding flow implementation Jun 13, 2024
@L03TJ3 L03TJ3 self-assigned this Nov 27, 2024
@L03TJ3 L03TJ3 mentioned this issue Nov 30, 2024
17 tasks
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