does emerge also have its own contracts? if so please make sure they’re properly labeled! for context builder codes have started with a focus on interfaces because they were the drivers of onchain activity with the most unsolved attribution problem still identifying gaps in what they’re able to cover well today and we’re continuing to sort that out internally been appreciating your feedback and patience as we sort it all out 🙏
nick prince
Product lead @ Base
Latest casts
hey just to clarify, we are not proposing a new type of mini app idea is to be less opinionated about the sdk builders choose. can just build a web app. use industry leading sdks like wagmi/viem share your metadata once in base.dev and your app will show up nicely in the base app, on our web leaderboards, and in other apps/wallets that integrate our metadata api (building this for farcaster and should be ready in april) we also launched a skill to easily convert any existing mini app to a web app, or can opt to maintain a hybrid approach
to start, we’re building an api for them to serve any app metadata uploaded to base.dev this ensures apps registered there can continue showing up in a rich way here in Farcaster, even if they don’t have a manifest. this gives Farcaster access to hundreds of apps that aren’t mini apps
base.dev is becoming the app store backend for the base app: one dashboard for builders to manage metadata/notifications and control distribution web apps, no custom SDKs required next: new discovery surfaces inside the base app so users find great apps faster, starting with popular apps leaderboard working closely with farcaster/neynar to drive towards standards so builders register once and get distribution across every growth channel on base. starting point is passing metadata back to farcaster like we're doing for the base app as always, welcome feedback onwards