Design Everydays

Pain Points

on mobile, when connecting to a wallet that has a wallet browser, i never get the option to connect without being pushed into the in-wallet browser.

i want the choice to only connect.

option to open in-wallet browser or stay in your native browser

option to open in-wallet browser or stay in your native browser

https://zora.co/collect/zora:0x5abf0c04ab7196e2bdd19313b479baebd9f7791b/73

Where does this setting live, in @walletconnect?

Staff PM MetaMask SDK 🦊[prev: scribd, metalink, 2x founder]

In WalletConnect we always keep the user in the native browser 

Redirecting to the in-wallet browser is not an option

Personally I find this feature because native browsers are always more reliable

Then why does the above happen? Happens to me every time I click CB wallet or MM in chrome. Get deep-linked to the wallet browser.

Those are non-WalletConnect connections

Dapps can choose to integrate the proprietary SDKs for these wallets which support their specific behavior 

MetaMask supports both WalletConnect protocol and in-wallet browser while Coinbase only supports the in-wallet browser

Wow I learned someone today, very helpful thanks @pedrouid.eth 

1000 $degen

All of your crypto. All of your wallets. All in one place. Your home for everything onchain. wallet.coinbase.com

Also knowing this now, no reason why @coinbasewallet and @metamask can’t implement this option for devs.