Dan Romero
@dwr.eth
Because: 1. Embedded wallets work reliably on mobile. The issue is the mobile operating systems have poor support for switching between apps, especially if it requires multiple rounds. 2. Most people in the world don’t have a wallet
9 replies
8 recasts
64 reactions
Jonny Mack
@nonlinear.eth
now share the tradeoffs :)
1 reply
0 recast
5 reactions
Dan Romero
@dwr.eth
1. Power users already have a wallet they want to use For the most part, these power users don't use apps. And for the power users who use apps, most are fine using the better UX. Thus, why the market is the way it is.
1 reply
0 recast
3 reactions
Jonny Mack
@nonlinear.eth
problem is that its not actually better longterm, but worse ("death by a thousand cuts"). embedded wallets create more problems than they solve. users are realizing this
3 replies
0 recast
5 reactions
Jacek.degen.eth 🎩
@jacek
Maybe Warpcast just becomes a wallet with social as an add-on. If it’s listed in WalletConnect, you can use it with any dapp. The business model seems to be taking a cut of swaps and mini app activity, so if the wallet is the core product, social only matters to the extent it drives usage. Some users may only care about the wallet. In that case, it’s just another option—one with built-in mini apps and a feed pushing buy/sell/borrow/earn flows. If you want a quieter experience, use MetaMask. Over time, wallets likely consolidate, and Warpcast could easily be used outside its own app unless there’s some technical blocker I’m missing.
1 reply
0 recast
1 reaction
Dan Romero
@dwr.eth
It's how web2 works and has scaled just fine
1 reply
0 recast
0 reaction
Lucas | POAP Studio
@gabo
Yes ! Embedded is death by thousand cuts In the case bellow i would mind less of the sbt if i had the chance to select my eoa wallet to recieve them > https://warpcast.com/gabo/0x8738164a
0 reply
0 recast
0 reaction
