Varun Srinivasan
@v
Whats the best mobile <> mobile wallet integration that you've seen to execute a transaction? i.e. App 1 initiates transaction, App 2 (the wallet) completes it.
24 replies
4 recasts
36 reactions
seizersalad
@seizersalad
most DeFi PWAs provide a very solid UX for this
2 replies
0 recast
0 reaction
Tony D’Addeo
@deodad
my nits: requires two steps to connect: first to connect wallet, second to switch network in both cases you get sent to metamask but not returned to blob.farm, need to manually switch back delay of a few seconds from when you switch apps to anything happening
2 replies
0 recast
0 reaction
Drew Fisher
@drewf.eth
Just use a good wallet. Rainbow doesn’t prompt me to switch networks, nor do most other non-metamask wallets if you already have the network set up.
1 reply
0 recast
0 reaction
seizersalad
@seizersalad
Rainbow just allows apps to switch your network? Is there an approval flow? How is the user notified? Genuinely curious
1 reply
0 recast
0 reaction
Drew Fisher
@drewf.eth
They don’t switch your network at the wallet level. Each wallet connection has a current chain and optional chains. When apps make a request, they can choose what chainId it’s on or fall back to the “selected” chain. Requesting a switch changes the “selected” one silently. Each signature shows its chain.
1 reply
0 recast
0 reaction
seizersalad
@seizersalad
Oh cool, just tried it and it's a definitely good UX. How is it not at wallet level? For a user's wallet to generate a signature on a chain, your wallet has to be connected to that chain?
1 reply
0 recast
0 reaction
Drew Fisher
@drewf.eth
Metamask has a concept of “the chain you’re on”. In rainbow, frame, rabby, etc, it’s just whatever that app last asked for. Different apps can use different chains without anything looking different at the wallet level, the chain is only shown on the signature prompts.
1 reply
0 recast
0 reaction
seizersalad
@seizersalad
Yes, get all that technically. Appears a wallet UX choice. Rainbow (and others) treat added/approved networks as "we'll just send txns on this network whenever an app prompts us to do so." Essentially "abstracted network switching" Whereas, MM chooses to make it a direct action. Rainbow UX objectively better...
0 reply
0 recast
0 reaction
