Tudor π£π‘
@tudorizer
have we talked about composability? apps with embedded wallets inside apps with embedded wallets so you won the big pot on a @ponder prediction market. Well done! are you withdrawing the funds to your Warplet? are you withdrawing funds from your Warplet to Rainbow? are you doing the copy-paste dance across apps and devices? @vitalik.eth βs βone address per appβ statement was in the right direction, but issues of account management (beyond asset holding) become obvious. throw the new @coinbasewallet in the mix and UX friction increases. Iβd be keen to hear @dwr.eth and @henri take on how is Alice navigating all this. (thoughts inspired after hanging our with @sheldrake and @accountless.eth today)
9 replies
10 recasts
19 reactions
Dan Romero
@dwr.eth
Alice will use an app and the app will have a wallet. She won't really think about where it's "hosted". Just what functionality it provides.
2 replies
0 recast
4 reactions
Philip Sheldrake
@sheldrake
How does that address the UX challenge highlighted here? Am I missing something?
1 reply
0 recast
1 reaction
Dan Romero
@dwr.eth
What's the UX issue for the average user?
1 reply
0 recast
1 reaction
Philip Sheldrake
@sheldrake
I'm working hard here. You may need to help me! The only way I can reconcile your responses here is something along the lines of your definition of "average user" being someone who won't experience this fragmentation. Is that what you're saying?
1 reply
0 recast
1 reaction
Dan Romero
@dwr.eth
1. The average user doesn't have a crypto wallet today. 2. Users use apps. They will have balances within apps (whether they know it's a crypto wallet under the hood will be less common). 3. When they withdraw it will be to a bank account so they can spend. This will blend into cryptonative spend accounts over time, but ultimately most people will use an institution for their core financial needs. 4. web2 / fintech works for most people if they happen to have a balance in an app and need to withdraw it.
1 reply
0 recast
1 reaction