Product

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.

weird internet kid. helping Creators with /seemore. yapping on /okbanger. curating in /creators and /cameron. dev + veteran + HBS. 
seemore.tv/cameron 🫡

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.

Well, I’m somewhat a creative myself. 

An ‘old’ game development type person. 

Previously VP of Product at Animoca Brands. Now on to something new...

do you have more info about this? 

would like to get smarter here

Basically, once an app is commercialising, there are restrictions as to how e.g. method must go through platform. With a lot of Web3 apps still be incredibly value transfer focused, this can get messy. A browser is a bit of a loophole.

wait wouldn’t this imply you want to push more actions to the browser vs in app?

They do, although the wallet is signing, all activity is happening in a browser. The in-wallet browser due to it being a far better UX than it pushing to a browser on the device non-app native. Plus, developer controls the browser and its behaviour.