Content
@
0 reply
0 recast
0 reaction
Jorge Schnura
@schnura
I've always been puzzled why in Web 3 everyone builds web-first products instead of mobile-first (meaning proper native mobile apps). And then we wonder why there's no mainstream adoption...
3 replies
0 recast
7 reactions
Steve
@stevy
true, also so many libraries / frameworks that are out there are lacking native mobile support
0 reply
0 recast
0 reaction
Andrey | Goverland
@sche
1/ At Goverland, we are building mobile-first, and it is indeed a tough path. One of the core challenges is creating a mobile-friendly crypto identity. Falling back to email as a crypto identity is, in my opinion, a false path to adoption. This creates a natural barrier for mobile dApps, where users need to connect an external wallet (or, even more challenging, create a crypto identity from within the mobile dApp itself). This is similar to the situation with emails: it doesn’t matter to Web2 apps if users created an email account because they needed to send messages first or because they needed to use a Web2 app first. Web3 users face the same challenge — they need to create a Web3 identity (wallet) because they need it to use a dApp, or they start using a dApp because they are already in the Web3 ecosystem and have a Web3 identity.
1 reply
0 recast
0 reaction
marv 🛸
@marvp
It's less about the platform than the solving of pain points. Adoption happens with killer apps which are *significantly* better than web2 offerings.
0 reply
0 recast
0 reaction
