Content pfp
Content
@
0 reply
0 recast
0 reaction
Cameron Armstrong pfp
Cameron Armstrong
@cameron
Why are wallets so focused on in-wallet browsers? Is it because: - There's no reliable way for wallets to always work w the native browser - There's a user signal that I don't see bc I'm not working on the problem - Hubris - Something else? Feels weird to work on two gigantically hard probs at the same time.
10 replies
0 recast
13 reactions
dawufi pfp
dawufi
@dawufi
because wallets aren't browsers yet
1 reply
0 recast
1 reaction
frdysk.framedl.eth pfp
frdysk.framedl.eth
@frdysk
This is why @dawn on ios is superior in every way for daily onchain activities, seamless To me at least
1 reply
0 recast
0 reaction
YES2Crypto 🎩 🟪🟡 pfp
YES2Crypto 🎩 🟪🟡
@yes2crypto.eth
Always assume possible nefarious use Tracking TRACKING
1 reply
0 recast
0 reaction
timdaub pfp
timdaub
@timdaub.eth
It is probably related to the technical constraint that these inter-app intents are unreliable and can lead to a lot of churn and bad UX for the average user Rainbow is one of the teams that is admittedly trying the hardest UX wise, and still most of their dapp wallet comms barely work
2 replies
0 recast
3 reactions
Peter Ferguson pfp
Peter Ferguson
@peterferguson.eth
With 7212 coming through we may see them just be fully integrated in the browser in the future This is what we hacked on at ETH Global London https://ethglobal.com/showcase/spc-wallet-service-xn68p
1 reply
1 recast
2 reactions
vani11a pfp
vani11a
@vani11a
What about a single app that is a browser, wallet, farcaster client, etc. the pieces are composable so users only add the things they want. Devs can create their own apps for use within this “super app”. Instead of a wallet with a shitty browser or a browser with a shitty wallet users compose an app that works best
1 reply
0 recast
1 reaction
MOΞ pfp
MOΞ
@moe
The primary reason is that walletconnect is pure fucking garbage. So wallets HAD to add in app browsers to make things work more consistently
1 reply
0 recast
1 reaction
Zeronium pfp
Zeronium
@zeronium
Point one, and application utility and skirting mobile app store policy. Functions and engagement native to the app can come under different policies, which browsers are not.
1 reply
0 recast
0 reaction
bobby pfp
bobby
@bmd
i think bc - deep linking ux is buggy and unfamiliar - some revenue opportunities for wallets rely on eyeball traffic and/or habit, a (good) browser gives users a reason to open the wallet - wallet retention really bad. most people onboard to use a specific app, then never come back. browser can help w discovery
1 reply
0 recast
0 reaction
Branksy Pop pfp
Branksy Pop
@branksypop
agree I don't quite get this feature I have now on metamask mobile. I supposed it's the same reason mobile apps integrate in-app browers. To make people stay in their env.
0 reply
0 recast
0 reaction