Content
@
0 reply
0 recast
0 reaction
Jonny Mack
@nonlinear.eth
hot take: due to being domain-specific, smart/embedded wallets create more problems than they solve if you have 5 different accounts on 5 different sites and there’s no way to easily unify them, or make them legible as 1 identity, thats broken web2 all over again but with (a lot) worse ux. tf are we doing?
21 replies
64 recasts
139 reactions
Dan Romero
@dwr.eth
Trying to make UX usable on mobile for normal people
4 replies
2 recasts
29 reactions
Jonny Mack
@nonlinear.eth
🤝
1 reply
0 recast
3 reactions
Dan Romero
@dwr.eth
Agree it’s suboptimal, but asking normal people to set up a wallet is worse imo
1 reply
0 recast
4 reactions
Jonny Mack
@nonlinear.eth
agreed—not suggesting that. just pointing out that we need to Do Better. smart/embedded wallets are great little short-term ux hacks. long term, they're a garbage fire. good tech considers the lifecycle of ux, not just onboarding
4 replies
0 recast
4 reactions
Henri Stern Ꙫ
@henri
Thankfully this is one of the most vibrant parts of technical experimentation in the space. There are a number of ways to build a superstructure enabling users to link, merge and manage accounts. Yours is an expert problem (that I also have) that we must solve for. But we also have to make it easier for everyone to come onchain.
1 reply
0 recast
2 reactions
Jonny Mack
@nonlinear.eth
i don't think classifying my description of the situation as an expert problem is helpful--its the default state for any new user who interacts with a handful of products. use moshi, bracket, and drakula and bam, this is what you now have to deal with
1 reply
0 recast
0 reaction
Henri Stern Ꙫ
@henri
Fair enough. What I mean to say is that each product has to be good enough on its own to start and we have to find a way to make it seamless to move from one to the other without loss of context. But it’s important to walk the path from both hands: helping the product function seamlessly on its own and the user manage their assets and data across them intuitively. Lots to do (and lots being done) but I think dismissing the progress as web2 but worse misses some of the point regarding accessibility in favor of (very valid but higher context) concerns. We have to fix both for things to work.
0 reply
0 recast
1 reaction
