Content
@
1 reply
0 recast
2 reactions
sparkz
@jacy
genuinely curious why so many project founders choose embedded wallets v. connect. as a user it feels like death by a thousand paper cuts.
8 replies
2 recasts
23 reactions
Jon Commstark
@commstark
agreed I loathe extra wallets and i end up not funding or using the app
1 reply
0 recast
4 reactions
Jonny Mack
@nonlinear.eth
because they're willing to tradeoff their app's onboarding experience for the user's wholistic web3 experience
1 reply
0 recast
2 reactions
Garrett
@garrett
simpler onboarding and embedded wallets provide a more unified experience. Some founders also want to show wallet metrics from wallets created in their app connect could be with a dozen different wallet providers across different web and mobile specs; lots of edge cases with connect bc EVM wallet space is so fragmented
1 reply
0 recast
1 reaction
christopher
@christopher
Wallet browser extensions are prosumer.
1 reply
0 recast
0 reaction
Lucas | POAP Studio
@gabo
cc @pedrouid.eth would have a bit of experience !
0 reply
0 recast
0 reaction
itai (building dynamic.xyz)
@itai
It really depends on what you're trying to solve for. For some usecases where crypto is in the background, e.g. a DEX trying to create a CEX experience, a global payment app, an NFT marketplace etc, it makes sense to abstract wallets away. In others, it doesn't make sense for all users, but does for some (especially where you use the wallet across apps, where ecosystems/global wallets can play a role). So in short, depends on what you're building and whom your target audience is.
0 reply
0 recast
0 reaction
JB Rubinovitz
@rubinovitz
Connecting an external wallet works for me 20% of the time and takes like 5 actions
0 reply
0 recast
0 reaction
Philix
@philix
Wallet connect and the likes are most suitable for the web. Embedded wallets are sure to work in any environment
0 reply
0 recast
0 reaction
