masvelio
commented
9 months ago point 2 because it is assumed that other components/subtickets are completed so this is a matter of putting it all together into one piece
Closed sachben91 closed 9 months ago
masvelio
commented
9 months ago point 2 because it is assumed that other components/subtickets are completed so this is a matter of putting it all together into one piece
User Story
When I attempt to create a community on Common, I should be provided with options for different ecosystems that my community in Common can exist in. Once I have selected an ecosystem, I should be prompted to connect the wallet or sign in with magic link that is compatible with the ecosystem that I have selected
Product Specs
options for ecosystems: Ethereum, Solana, Polygon, Cosmos
compatible sign-in options: The Figjam lists out the flow for a user creating a community. Depending on what ecosystem the user selects their sign-in options are limited to ones that are compatible with the ecosystem. For example: If the user selects Ethereum, their options are to connect to Metamask wallet or sign in with magic link. If they are already signed in, we must check if the method of sign-in is compatible with an Ethereum community (also detailed out in the Figjam)
12/4 update after call with Marcin: If a user is not signed in and they land on the create community flow, they should be allowed to select an ecosystem without signing in. Once they have selected an ecosystem they will be prompted to sign in with a wallet that is compatible with the ecosystem they selected.
Once the user picks "connect a wallet" or sign in with magic, they are directed to sign in. This sign in component will reuse the existing components we have When a user is signing into an Ethereum, Cosmos, or Solana community.
Link to Figjam
Designs
Link to figma Mobile Screens
New Components
Acceptance Criteria