How to scale your products and democratize access to the decentralized web

ProtoLayers Talks · June 2024 · 15:17

Francesco Andreoli of MetaMask discusses the paradigm shift and principles of building in web3, including MetaMask Snaps and frameworks for scaling around developer communities. The talk focuses on how to grow a product and democratize access to the decentralized web, using the wallet extension platform as the example.

Speakers

Topics

From ProtoLayers Talks, hosted by ProtoLayers.

Transcript

I just arrived from the airport so I hope like this is worth it anyway cool this is kind of a preview of of my presentation uh that we have on Saturday it just skimmed a little bit more on uh how many of you guys heard about snaps yeah so I just want to walk through a little bit also like what what's behind snaps how we started why we want to do more permissionless Innovation stuff and uh yeah how many developers do we have in the room just trying to understand the level that it's more like chill so it's uh I can go a little bit everywhere so yeah this is a a picture of me back in uh in Denver H and yeah I've been I've been around the ecosystem driving not just Enterprise blockchain but also like permissionless uh blockchain and then that snaps was one of like the

major uh kind of uh initiative that I help support and uh I'm all about like this permiss list Innovation trying to build modularity and build further products around uh uh around uh around activating much more the the community and uh yeah I just help cool developers building cool stuff around different products from the starts to down the funnel so if you guys you know need to deploy your products obviously consists the modern umbrella so you have like from stuff like infura I don't know how many of you guys have us used infura in the past basic you have infura you have like obviously metamask you have flask for developer environments uh Linea obviously for a z KVM and uh yeah I'm I'm I'm not getting started with chess

but I trying to get better so if you guys want to play with chess and and I I can always learn more cool I want to understand a little bit like what's what's the future of wallet look like I have no idea how it look like I can tell you how it doesn't really look like I'm not a big believer you know like P PVP right I don't think that we will uh uh you know we will have like one personal journey of every users out there I think like we are diversifying Journeys uh we will have different needs for different not just user but also for different developers we already saw that right you have people that are more defi heavy you have more people that are uh let's say nft heavy they just want to deploy their collection and uh and uh and don't rug

pool hopefully but uh but uh but yeah so you have personalized Journey so different people that are kind of driving I also don't think that one entity uh knows best back in the days we had something like 7,000 open repo in our uh metamask uh uh code and basically what we said is it's impossible to keep up with the Innovation right and uh everybody's coming with like native integration everybody's coming with like hey integrate us use our own API and trying to kind of like Leverage our technology and then we ask ourself how we can actually build something that is sustainable and we can keep up with this Innovation around the the ecosystem right so uh I kind of like resume here like this five principle right so

obviously like we want to build with uh thinking about the user Journey try actually understand that the user want to have transparency want to have kind of like consent is is King they want to understand what to revoke which access to give and uh it's quite actually powerful right so a lot of products today especially in web 2 you have no idea which actually accesses you're giving and how you can revoke those accesses right and uh obviously there are some tooling but a lot of like for the average users uh people don't know so Trust basically like what you want to build is a fully transparent system you want to have actually ownership of who is building building what and uh uh attribute accountability and and uh basically apart apart of that there are

different ways right this is the third pillar and uh obviously like we want to not just decentralized our product I don't know if you saw like within fura we have din decentralized uh infrastructure provider that is actually kind of like this this decentralized RPC uh but uh but apart of that people want to see much more transparency and modularity around the uh building a product right why also we are doing this is mostly because uh today we are getting you know very let's say active feedbacks from the community but in the same time we have no idea how to make make more the community active really contributing to like product development and this kind of like permissionless road map so this is kind of like one

things I really like we're building a universal web tree uh interfaced by empowering Builders right this empowering Builders is not just giving feedback but actually contributing to uh code and contributing to uh functionality and that's basically where kind of snap started snap started back in the days at Devcon I think two where Dan started to say okay how we can build an onm compatible chain with Cosmos and uh and then kind of it started this kind of Cosmos uh snap but uh but that's kind of was the beginning and then we said ourself okay how we can build further uh some product functionality that's basically what snaps is today if you guys go on snaps mamas. this is like the the allow list of what uh these 50 plus naaps are allow listed today but long

story short is that uh you can extend the functionality of what the extension does today uh through snaps right so Snaps are in a silo I will I will go a little bit I don't know how we're making time I hope I'm not speaking too fast but uh I'm trying to trim the the slides that I thought like were interesting uh those are kind of like the the six use case uh that we I mean that I want to show a little bit today but inter probability is the one about nonan compatible snaps I don't know if you guys use either the snap or BTC snap or uh there are different like non evm compatible snap you can do Native transaction with notification is super interesting you can you're able to getting notified if specific event triggers and we see that a lot of

traction with with a cool Trader could be nft could be defi heavy uh users on AA we have some NPC and2 a phas naap for account recovery that's also like quite interesting um I will show some demo if I had more time but um uh couple of things to understand right because that's a question that we are getting asked a lot around like you know snap security basically like Snaps are nothing else as like an mpm package and they're fully isolated from the extension so every everything that you are asking the snap to do require a direct permission from the user to get access to and uh so that's also like one concept is super important what does it

mean this is not only the permission that you're asking for users but is also very powerful for uh let's say parties to build a isolated snap because it can interact with also your own API so a lot of Technology you know a push notification can build their own snap with their own API and I think that's also like quite powerful value proposition because today if you're using the DAP API from uh from the extension you can't interact with with your own product directly uh this is for example the wallet guard snap there is a full category called security I'm using for example like one one similar but basically like every time that you're signing a transaction he cross check if you're interacting with a malicious or no malicious account and uh that's

basically like kind of the D that you can see also like what's happening right you you know exactly where the snap is hosted you know the outer you know also the permissions here are some of the permission when you're accepting basically like installing the snap even like accessing the internet you can give or re revoke permission and uh whenever you installed it will appear on your setting and uh it's quite straightforward right it's not really rocket science I think everybody using I don't know WordPress plugins or like some safe uh safe plugins too and it's very similar so just to recap so fully self custodial right so they're interacting with their own API with your product but in the same time you have fully ownership on what transaction are happening to the

extension um and basically like users uh are being able to fully interact with which snap they want to they want to interact if today you want to use your I don't know your Solana snap interacting with the Solan ecosystem tomorrow you're not interested to do that anymore you can uh you can basically like uh uh revoke the access so for the users here you guys want to check this is like a full kind of like guide uh around snaps with the four main categories right interop uh security communication account management uh one thing is very interesting on the account management side there is a one uh snap called transaction insights and uh you get really like cool things that you can see around transaction flagging up trans action interacting with malicious smart

contract and for you guys that want to start building uh your your snap here are some like kind of like wish list code examples and repo that you can actually like fork and build from it uh we have also like a full snaps Builder program that's is also like quite quite interesting so this talk was a little bit about you know why how you want to build further your products but in the same time how you can scale much more activating the community and I would just want to State this here right that you know building a cool technology is not enough so znap is at the end a piece of uh um mpm package added to an extension and what you want to do also

like creating the full ecosystem around it right you want to support the developer helping out give code code example but most important right how we can Define different Frameworks around how we can build further your products and scale your products and that's basic Bally kind of like the next section so in the past maybe one year and a half I've been discussing with a lot of like devs anybody Devil's here okay so I can also speak something random no one will understand but uh I've been uh I've been trying to kind of like Leverage um like to speak the same language for different developer activation today and I came up with different Frameworks right so we can really like Define how is a full developer funnel how is kind of like a

uh like really what are the builder needs uh around like uh around different products and I started doing that with snaps but also like I started also to uh get more an holistic view on that I don't know and uh and basically like this is one of the two Frameworks that we show you today um and I asked myself you know what are really the the builder needs outside uh and uh you know why we're not really aligned because a lot of people are starting with different activation from top to bottom then you still don't know what really like devs one want to have like the kind of the at least the MVP of getting your devs on boarded and uh I started like thinking about this I remember this from 10 years ago uh this uh what was that the maslo

hierarchy of needs and then basically I created this uh uh Francesco hierarchy of builder needs and uh basically like this is nothing else as kind of like the five levels of a must have as a developer ecosystem to kind of like it's cool to have right so I'm not I I wrote a full like paper on that but basically like the the kind of the basic needs are obviously like you want to have a strong access to resources you want to have your education on points your docks need to work you want to have you know I mean it's an no-brainer but a lot of people are saying hey franisco let's let's do you know virtual acon without actually having a 10 minutes walk through tutorial uh in your docks uh and uh it's kind of self explanatory but a lot of

times is is is really like hard to to make people understand that's why I create these kind of Frameworks so and and then you you go like up one one way and you're saying okay before even like shielding your product on the face of developer what you want to do is building much more a safe space around around the topics so kind of like driveth through Tropic topics instead actually going directly uh example right instead saying okay let's deploy this on linear or or any other layer tools what you want to do is uh let's build us a dep from scratch and let's understand you know why you know what what what are different deployments meaning for you as a developer why I don't know there are people that are different game game deps are different than you know protocol

deps for for specific use case right and then you have different ones so I will not deep dive I'll just leave you guys uh I think we're almost on time give you guys this Q code that's basically where kind of like all the uh all the description is and I will send you the the uh I can send you the paper later so the second framework and the last one then I let you uh guys go uh it's all about you know know um we want to focus on curiosity we want to understand but at the end of the day we want to understand also where you are in The Funnel of this developer acquisition so you want to understand okay those uh developer Workshop are not working why are not working because maybe they're too specific maybe they're not working because people are not trusting you that

you're building that you are building cool stuff and basically this is where I kind of like came out with this second funnel uh it's very specific but basically it's kind of like a developer engagement funnel and I can like I don't know I speak a lot with different ecosystem players but I want to say that around I don't know probably like eight out of 10 companies they're only focused on product specific conversion right so everything that you see down in the light blue is all about uh uh very strong like Pro product shielding in the face of developer varing very Workshop focused on uh on boarding developers and a lot of time we're literally like not doing the uh other part and uh that's basically what I call like value driven

on boarding uh and that's nothing else as driving you know ecosystem Community calls as driving like uh um Builder like what we're doing with Builder nights around vertical focused uh topic like 437 even before saying hey build a smart account or something like that like you know very high level uh uh topics that can be debated on like on a Thor leadership kind of level and getting this kind of Thor leader is extremely important because you want to show that you are on top of those narratives and uh yeah it's quite funny because I put here the value The Shield free zone value based programming right and then here is like more like a shieldone and developer marketing where

you get involved like pmm and much like people in your organization that are that has the goal to convert uh but a lot of time this need to happen uh on a second time right it need to happen later so cool I think uh uh we are there I hope I didn't bore you but quick recap right uh so we want to build our products through like permiss Innovation fully modular uh it's key we don't want to activate just developers with like you know opening issue in in our uh in our repo but you also want to have uh instruments to Advanced and extend the functionality of your products you want to build a ver bur uh developer Community around your product so

building a cool Technologies is is not enough and most important right if you want to have uh fully a web three fully accessible for everybody uh we need to build always thinking about user Centric narrative but also thinking about this need to be fully permissionless I hope it's it's a little bit clear and thanks everybody for the quick 10 minutes of your attention [Applause]