[FEATURE] Improved authentication userflow

[JeffreyDoyle]

Feature

A common area of difficulty for users of Flow Wallet is moving assets between their Cadence and COA accounts on EVM on Flow. It's often unclear to users why they have multiple accounts on Flow, and why they need to move assets between their accounts when authenticating with applications on Cadence and EVM.

Solution

During authentication with an application, Flow Wallet today automatically selects to use the account that's compatible with the application. If the application is on Cadence, Flow Wallet will automatically select to authenticate with the user's Cadence account. If the application is on EVM, Flow Wallet will automatically select to use the user's COA on EVM on Flow.

Flow Wallet must make the account that's used during authentication more explicit to the user. The user should manually choose which account to use, similar to what they do today with comparable products like MetaMask when they have multiple accounts managed by their wallet.

When the user selects which account to use during authentication, all accounts maintained by Flow Wallet must be displayed in a new 'account selection' view. However, all accounts not compatible with the application must be unselectable/disabled/greyed out. This way, the user must choose explicitly which account to use. Therefore, they will be explicitly made aware of which account they're using within the application, and therefore better understand why assets must be moved to the account they're authenticating with that application.

After the user selects which account to authenticate with, they will then be able to move assets (FTs and NFTs) to the selected account from each available other account.

Requirements

• The existing prompt to move assets at authentication is removed.

• The user to select which account to use when authenticating with the application.

  • Only the accounts maintained by Flow Wallet that are compatible with the application can be selected, however, all other accounts must be displayed in an unselectable state.

• The user is able to move assets to their selected account using the existing move assets mechanism.

Expected Outcomes

• Designs complete
• iOS implementation complete
• Android implementation complete
• Extension implementation complete

Platforms

• iOS
• Android
• Extension

[JeffreyDoyle]

Mobile Designs: https://www.figma.com/design/mSr5uIApRJNrpkmN0YNuD6/Flow-Wallet-Mobile-Design-v2.0.0?node-id=40814-7235&t=BwEWbDNZjkzxIDUt-1

Extension Designs: https://www.figma.com/design/Qs5stGXY2US8Dj8UDjsdQ5/Flow-Wallet-Extension-Design-v2.0.0?node-id=48-117&t=dLPVsdURemDb8dAO-1

[JeffreyDoyle]

@KK-UIUX -- We can finish the corresponding extension designs and then add the link to this issue.