New Ethereum talks, every Monday. The week's conference uploads by event, in your inbox.

Loading player…

Mini Apps BBQ Week: Mini App 101 Tuesday

BaseThu, Oct 9, 2025, 12:00 AM

These workshops are run by our internal Developer Relations Team, designed to teach you best practices coming from real-world Base experience. #OnchainAppInsights #web3 #accountabstraction #erc4337 #onchain #onchainApps #gasless #base #basechain #coinbasewallet #crypto #web3 #apps #blockchain

Transcript

How you doing?

We are live. I'm doing good. So, good to be here.

Yeah, good to be here. I'm excited for this.

I'm so excited to go through and elevate all these mini apps. I can't This is the first time that we're doing a base builder bar. Sorry, BQ. Look, I've been around Australians all week, so it's not my fault.

Yeah, that's a good thing. Australians are cool. But yeah, what are we talking about today? We're talking about mini app.

What?

We're going to do a big mini app deep dive today. Hell yeah.

Yes. Yes. Everything people need to know for building mini apps. And these run across base TVA app and Farcaster. One protocol powering two applications.

It's something most people have never experienced before. So yeah, exciting. Yeah,

it's amazing for your users and it's amazing for developers. It means that you as a developer, you're getting access to these two very big ecosystem applications and you're getting distribution for your app, which is awesome. And then on top of that, as we all know, mini apps are just web apps.

Yes,

it can work. Yeah. So like even existing apps like should never feel like they can't be a mini app that it has to be something brand new, which I think is really cool.

Yeah. I feel like you're answering the question like the number one question people are asking. You say the word mini app to people. It's like you know what is it? Um you know let's let's try to answer that like what is a mini app and like why should someone want to build it and is it really mini at all?

Yeah. I mean is it mini at all? Not at all. You can have incredibly rich um rich experiences in a mini app. It's up to you as a developer.

you determine like how extensive it can be which I think is really cool and why building mini apps like I mean there's so many reasons but the reason why I'm pretty bullish on mini apps and not because I work at Baze is mainly because you're like as a app developer like one of the hardest things to do is getting users and the reason is is that we have to maybe it's through SEO it's maybe through social ads there's all this like push and friction in that you as a developer have to do also a product person has to do you got to find the users that's and that's hard in itself right but then what you can do with a mini app and why mini apps are powerful because your mini app exists without download friction without having to go to an app store apply to have your app there pay a lot of money to make sure that like it it's showing up in the search correctly you don't have to do that with mini apps mini apps they just work out of box. Of course, they have to be have a few things and we'll go through that, but it means that in the base app when I post a link, it is the mini app. So, it is like an a rich embed with a call to action that you can open up. My mini apps are being distributed by my users because they're social experiences. Maybe there's like there's all these things that you can do because you're leveraging a social network underneath the app itself.

That's what's driving like the distribution and having your mini app being surfaced by all these users.

Yeah. Do you mind if I like put it in another like context for people as well?

Yeah, go for it.

So you have Farcaster, you have TBA, they have their own, you know, millions of users, hundreds of thousands of users, they have the users, right? And then we as developers, we create these mini apps. And how we get access to these users is just by posting a link to our web app, right? And that's so different from the traditional app distribution and like go to market where you kind of have to submit your app, pray that the app store lords accept your app. All right?

And then when you're getting paid, they're going to get a cut of that pay and it's a large chunk of all your hard work. And then you don't even know if people are going to see your app, right? Like there's no distribution. There's no guarantee that people are just going to just jump onto your app versus there's a whole new paradigm of like there is no gate right come develop deploy it and then when you post it users will see it you know someone is going to see your app right because you have followers you have this social feed and you're posting it directly to the feed um this is crazy

yeah 100% I'm I'm with you 100% right there and I think like I'm going to share my screen now So forever, but it really does, we do go through this and on the why mini apps page on the base docs. We really go through like how we envision the base app flywheel that mini apps are these social lightweight social native apps. The more mini app the more people that are on chain or using the base app or using the Fcaster ecosystem, the more people the more builders because that's what builders want. Builders want people to use their apps. It's really not that simple.

It's not not that simple. It's not that hard. You know, we all want people to use our apps. We want to see our products succeed and stuff like that. And this is how we do it.

We create an ecosystem full of users that are ready to use your app because you've created this really rich experience for them. They share it, more people see it, so on and so forth.

Absolutely. Can you let's let's go a little bit uh a little bit deeper. Right.

We've been talking a little bit about mini apps and like the benefits of it, but like architecturally like what what is the difference? I want to know, hey, I know how to make web apps. I'm good with V. I'm good with Nex.js, but like what's the difference between that and a mini app?

What makes it so special?

Yeah, I mean, I'll go through some code examples of like the big call outs here, but the number one call out is that the mini app or mini apps will have access obviously to the Farcaster SDK or like some people use mini kit. You can also use the Farcaster SDK completely fine. Both are the same. So mini kit is built on top of the farcast SDK with additional hooks to make it easier. But you can also just use the Farcaster SDK to build a mini app.

So there's one. So like you generally have your whole app wrapped in the provider. The second part is the fact or there's I guess two more parts to this is that you have your manifest.json. So you have your f like you'll have your manifest route where you your forecaster.

json lives. And what will happen there is like I'll go through what what that actually looks like. But what happens there is like you are able to associate I am the owner of this mini app because I have signed this far. I've signed this to say this URL is my mini app with my farcaster account or my base app account now. So like that's something that is very important.

And then we have very rich metadata which of course we're going to go through as well. What this sort of looks like for you guys like visually is like when we have people are sharing your mini app and I have an ex I'll obviously share my phone here as well but you can see here I'm sharing out this I'm sharing this mini app is the the metadata is has the open CTA for the button when I open it is obviously going to open a whole experience it's not going to just open a website I haven't left the base app I haven't had to do anything else I haven't had to download anything another really cool hard is because you are using the farcaster SDK or the mini kit or mini kit and you have access to that Fcaster data you have access to the users you have access to context context allows us to understand like the user's FID the user's username so when I open that mini app it can actually say welcome SHI like it can feel like it's just for me and I don't see like I don't I don't think I've had any other web apps that can really just do that even before like we can just do that out of box. If that's the most simplest mini app you wanted to do, you can just do that today without any extra any extra uh issues.

Yeah, it sounds like a mini app is essentially a web app with extra it relies heavily on metadata first with the caster JSON allowing you to index and allow your your app to be discoverable between the different clients. So that's Farcaster and TBA. And then outside of that when we're sharing our mini app when we are you know we want to create these rich experiences the images the titles the person you know the personalization that's also metadata right and that's because we're wrapping the app in this provider but also because of the far the protocol right we are grabbing information from this shared protocol that's open

to all of us this is this is pretty sick did I miss anything when I discovered that

no absolutely so Yeah. So like as you can see on my screen, this is an example and this is also like a new page on our docs called sharing your mini app where we really break down like how the metadata works all together. How does the manifest work? How does the the metadata like the for your embeds work? So if we just look if we look here like we just see like obviously the button is going to say play now.

We're going to have the URL like where your mini app is going to la what you're going to launch all these things like put together create like a rich experience. It doesn't look like much. Like honestly, to think that all of this code will make a whole um personality quiz like the Powerpuff Girls and stuff like that. It's kind of wild because there's really not much else to it. Would you like me to show you how it looks like in code?

I think like that's the

Yeah. show us like what a project structure looks like and then I do have a question next on just like are there any like mobile considerations when building mini apps.

Yeah, totally. I'm going to show you guys like I'm going to oh have GitHub already open. So this is an example like a mini kit example. Here you would go into your app. We have our route.

This is our forecast.json route and then we have like our manifest. So everything that we're going to assign everything here is available in our EMV file. So the project name, description, all these things. This is needed.

This part is like where I these three lines here. This is me signing the manifest and therefore with a with a particular URL. Therefore I'm getting a hash to say like okay this person with this FID has signed for this URL and that's getting married together. So when you open a mini app and it says by Sohi or by Pat, it's because they have signed this correctly. Whoever signs the manifest is the owner of the mini app.

Really quickly, Sohi, I just want to point out to those watching that this is one of the two files, maybe three files that you need to have to change your existing web app into a mini app, right? like this is is one of the metadata that these clients will reference when you know kind of building your mini app right so this is almost like step one you know of converting your existing mini app in a sense is getting this taken care of

I think what's even cooler is I'll show you guys I literally just spun up like a next project I didn't change anything and then just by virtue of the things that I've added the next page is now like a mini app it's Just that easy. So then the other part is like I'm going to go into my layout and here from I'm going to highlight this for you guys as well. This is where our metadata for our embeds are coming from. And so of course like everything again is like being the way with mini what I love about mini kit is that I set this all up on my EMV in my EMV folder and then this is all populated for me. Like of course when I deploy to Vasel I update my I update all of my variables in Vel but that means that yeah I don't really have to worry about this cuz I know out of box this just works but I know not everybody is an XJS fan and that's and that's completely okay.

I guess what I'm just trying to say is like in your root at your in your route you just need to have the embed metadata in order for the mini app to work correctly.

Yeah actually

and again go ahead. Right.

I just wanted to say as well like another thing to consider especially for our existing app anyone with an existing app is the fact that you don't have to wrap your whole app. One of the really one of the mini apps that I really love um is called Fantasy Top. And the way that the developers did it is that they made one specific route and that one specific route had access to the metadata, had access to the the manifest. Everything was set up just for one route in the app to be an like to be a mini app.

Yes. So

which guys, what So explain is saying is that you may have an existing web app that does something right and maybe you don't want to convert your whole entire application into a web app. Maybe you want to experiment and you want to, you know, have a one small feature be a mini app. You can do that. The whole h the entire app does not need to be a mini app, right? Create a new route, wrap that route, wrap that page in the appropriate metadata, right?

Call the appropriate hooks and voila, you can just share that route on the page. And what we're discussing right now is the embed, right? And the embed is super important because it is what is going to kind of present and be kind of like the marketing page, the splash to your app, right? So, if you guys are just joining in, this is mini mini apps 101. And one of the questions I want you guys to put in the chat is or or answer, sorry, is why are you building a mini app and what do you hope your app achieves?

So, we have a couple people answering and sharing their mini apps down below, but curious on what everyone is building and you know, why why did you choose to build it as a mini app? Back to you, Sia.

Awesome. So, I'm just going to go through this is um some of you may have already tried it before. This is like my Powerpuff Girl quiz and this was made so I could show everybody how we can do like dynamic metadata which every day of the week we're going to go into a deep dive. So, today is the very holistic highle overview about what we think makes a really good mini app and things that we want to consider. So, I'm going to show you guys like how it all comes together with your with the embed metadata as well as the fucker.

json. So, here I am at the very top. You can see that this is a Powerpuff Analyzer by me. So, what that means is if Pat signed the manifest, it would say by Pat. Lucky for me, he did it.

So, that means that this is my mini app. This is like how the two things are coming together. Then when I close this, there are two things to see here. One of them is the fact that if I go and I can share it directly in the feed. So I post it in the feed.

You can see like as it loaded it was like a URL for a website but it it actually loads the embed. So that's how it all works together. If that makes it a bit easier to understand.

And this is you know we get this question all the time in Discord. How do I get my app in base? This is how you do it. Like you literally create a post and you hit the word post and that is it. It this is equivalent to applying and getting approved to get into the app store or your favorite mobile device, right?

Like that is this is it right here, right? You sign this manifest so that you can be cited and and and and you know your name is on this art. You know, your app is art, but like you get cited for your work. is credited to you and then you deploy it and you get it to the hands of users by making a post with that URL and that's it.

Yep, that's it. By virtue of me actually posting the mini app, if I go to search, I can actually just search it up to see Powerpuff. There you go. That's it. I made a post and that's it.

It's now available in the base app.

Wait, go back to the search real quick because I want to point something out again. So while the embed helps you to create that poster that beautiful like work of art to for your app, the manifest allows the indexing and searchability. So there's like two major questions like how do I get it out there? Well, you post it on the app. How do people find my app?

Well, make sure that your manifest is well uh you know filled out, right? Because without that TDA forecaster, they will not be able to index your application, right? So people won't be able to see

100%.

Yep.

And that's such a great point because what I can I'm going to share I wonder if I can share two screens at the same time. I might not be able to, but that's all right because what I really want to go through today with you guys is I'm sharing the doc screen, but I'm sharing a new page that came out literally 5 minutes ago called Miniapp Search and Discovery. Something that Pat just touched on is super important for you guys to understand is that we have a breakdown of how the metadata works, how how to make sure that everything looks good in your metadata. So it search when you search it, it looks great, things like that. But posting is part of the indexing process.

Without posting, you will not be indexed.

Yes. Also, when you want to update your manifest, maybe you want to change URLs, you need to repost it again. It has to be reindexed for that to update. That is just how how this all works.

If you want to know like if you want to go into like a huge deep dive, please go to uh miniapp/arch and discovery. That way you can go through exactly how it all works, how trending works, saved mini apps, because that's something I can show you guys today. You can just right click on I'll just show you in the UI, but you can save the mini apps that you love. And we're not supporting it yet, but we will soon as notifications. And the great thing is because we're building on open protocols, because we're building on the Farcaster protocol, the way that notifications are going to be handled, if you already have a mini app with notifications in Farcaster, it's going to work exactly the same.

And if you're using mini kit, even better for you guys because we ship with mini with notification examples. Everything that you need, everything you need to understand how to fill out your manifest and things like that is all available on our docs. And also we have guides um one particular guide called thinking social about social mechanics and sharing best practices because sharing is very important for your mini app. Sharing plays a very big role. This is how you're going to get distribution.

So make those call to actions for users. Don't make it spammy. Like

really think think through the process. But yeah, I'll get off my soap box. Sorry.

No, for sure. No, honestly, you're you you bring up a good point and I actually want to maybe pivot to that just a little bit on the sharing, right? Again, I'm going to ask you a question, but I just want to set the stage for for the audience. Right? We are sharing our application in a social feed where pe like people are already there.

Our use potential users are already there, right? And if you want your application to go viral, not only does it need to look good and work functionally, so that's your embed and your forecaster.json, but when they use the app, you need to build in features and functionalities. We have these hooks available. They're in the SDK, right?

That allows you to share something, right? It should get someone compelled to say, "Oh my god, let me share this app. Oh my god, let me save this app." Right? And the reason I bring this up is because there's a question in the chat of like how do I get my app featured in in in base app, right?

That is the featured section is driven by interactions, saves, likes, shares, right? And so that is why thinking social is so important because you want like that is what is going to drive the adoption. That is what is going to drive the verality. That is what is going to ultimately drive you to get featured and and get your app in more hands, right? It's kind of like a meme.

When a really good meme is there, people want to share it. No one's like, "Hey, you should share this meme." Right? You automatically feel compelled to do so. So, so if you have any other thoughts on that, please.

No, I think like you're really hitting it. Yeah, that's exactly how it works. Like we need to for your mini app to show up in the category section for it to show up in trending and things like that. We need to there that's been driven because of engagement. So how often are your users like sharing the mini app like without that data it won't show up in the trending section.

It won't show up in it won't show up in categories categories in the base app only for I know we're working towards the top 100 mini apps. So you have to yeah you have to have a high level of engagement if for for those to be surfaced in those things. However, but also just making sure that your mini app is something that people want to use. I think like that's the number one thing. It's not going to be just the fact that you're featured.

It's

the fact that you actually have a really good app. And I think like we can go through like what makes a good app or what makes a good experience.

Yeah. And I think we're going to cuz again this is like a week long thing. We have a UX track. We have a thinking social track. So don't worry guys, we're going to go over this.

But the TLDDR is being featured and being a really awesome mini app is a byproduct of making your app awesome and making the UX great and making it something useful for the people. So you want to really focus a lot of your effort in that part, right? Clean UX, you know, useful um and and and and think social, right? Like how how would other people use this if this is going to be on a social feed? Like what is the benefit to the users there?

the virality is going to be a byproduct of that.

I think

Yeah, go ahead.

Should we go through because I think like thingu works and things like that. Why don't we go through like a mini app that from the community that we really love. Why don't we do that cuz I think that will help.

Let's do it.

So, let's go through. Okay. I am going to show my mobile phone again. As long as it opens. Awesome.

Okay, it's sharing. Awesome. So, I really want to give a shout out to this uh to Zeni, the developer for stream. I really love this mini app. I know we talked about it last week, but there are there are multiple reasons why I love this mini app, why I think this is like really great UX.

When I first opened this mini app, it actually opened with this tutorial um set up for me. It's a really good way for me to understand, oh, okay, I've opened this mini app. What does it do? It goes through an awesome little uh step modal. I love that.

Like the animations are just a byproduct. Like the you can tell that there was a lot of time that went into this mini app, which is super cool. It goes directly into like what it does. I feel pretty empowered. Like now that I know what it does, I'm more likely to want to do something with it.

Then if I go to my claims at that point in time, I'm I want to go and see if I can claim anything, right? I feel like that's the right time for me to and it's it's up to everybody but like that's for me the right time to like authenticate. I'm either going to we we will have blind signing available soon but sometimes with mini app experiences there's nothing wrong with allowing a develop allowing a user to look at your app and understand what it does before asking me to log in. Could we could we like take a second on that one really quickly because I think that's something people can implement today to increase their UX like double, right? So, think about this guys.

If you're building a mini app or any app, right, and to put yourself in the user's position, uh, you know, point of view, if you want to check out something really cool and the first thing it asks you to do is create an account, log in, and do all this, you don't even know what the app is yet. It's almost like when you go to click an article online and there's like a payw wall like you're like, man, I just want to experience this thing first before I go ahead and make a payment or login or create an account, right? The more friction you add for the user, the less likely they are to go back to your app. We also have to remember like people just have low attention spans and it's okay. We've, you know, we've grown to to to be where we are today.

There's nothing we can do about that. But you want to keep this in mind. It's like how can I make this snappy, easy to use, and only add friction after these users are bought in.

Yeah.

Secondly about this is that with wallets, when you're using mini kit to build your app, you don't really need to think about wallets or connect signin buttons or anything like that, right? Because it will automatic automatically connect in. You got to remember these apps live inside TVA. TVA is an everything wallet. TV is an everything app including a wallet.

So you don't need to add another layer of wallets while in the app. Build your app, use mini kit. We got all the other like auto signing happening for you, right? Assume your users, especially when you use mini kit, assume your users have a wallet and are going to be able to log in automatically. So no need to recreate that flow

100%. And maybe if you're not using mini kit and you just want to use like WagMe and VH just by like because that's how you want to build your mini app, you want to use the podcast SDK. The really great thing is like in the docs, we have the code ready for you. There's already code snippets that you can copy directly and just paste into your app and you'll have the same experience where I log in, I silently log in, my app is already connected and things like that. And I think that's that's such a great that's awesome UX from like Pat's perspect from what Pat was just saying.

And yeah, of course on chain kit the wallet component, you don't need to do anything except render render the component which is kind of wild. Awesome. So I guess like we've gone through we've talked about how metadata works. We've talked about how embeds work. We've talked about how your manifest is what determines like where your mini app is going to show up.

All this information of course is in the search and discovery guide that we have available in our docs. Creating rich embeds that's already there in our sharing guide as well. A really big thing that while we were just talking about like how onboarding works, how you we need to be thinking about how users are opening our app for the first time. What does it look like? What does it feel like for them?

A really good point to call out here is um mobile first. So your mini app is going to be opened as a mobile application. I'm just going to open this up. If this was not a mobile first design would make it would mean that I would have scrolling issues. It would be too janky for me to even like comprehend what's going on.

So please like when you're making our mini mini apps like mobile first design principles, make it clear, make it concise. There isn't a lot of screen here. So we want to make sure like whatever we're doing like let's make the most of the space that we have.

Two questions. One is Dylan okay with us sharing this mini app cuz the people

Yeah. All right. Cool. And then two, we're kind of going backwards, but it's fine, right? The question came in is like, if I use privy for login, can they log in to tbate with that?

And the answer is yes. Like yes, you can have privy in your mini app, but then you're creating a wallet on wallet. Like there's a wallet inside of the wallet whole thing, right? And I want you guys to also think a little bit larger, right? So remember TBA is your wallet.

Wait, so do you mind like exiting this mini app for a second and then just going to like the wallet page?

So this close.

So if you allow your users to sign in with TBA. Oh, no. I want I wanted you to show it, but it's okay.

Oh, yeah.

What? Let's say let's say they go to one mini app and like they really love it and they earn tokens on that mini app. They can use that same wallet, access your application, and all of their like funds, their tokens, their rewards are all associated with that wallet. They could then go on Shopify and go purchase their goods using that wallet. you want to think about the UX because if they're using a Privy embedded wallet um and then maybe they earn on an application there, it may not be as intuitive uh for you know people just coming to crypto on like how do I move my funds from this embedded wallet.

They won't even know what an embedded wallet is, right? Uh over to my TVA where my where I do most of my stuff, right? I'm I'm social here. I'm messaging friends. I'm earning from my post, right?

I earn everything in my TBA wallet. Now why do I have to like get you know so you want to create a really cohesive user experience and that is done through using base accounts and someone did mention in the comments sub accounts yes sub accounts will solve this right and start building your app with a base account mind first that universal wallet is going to allow you to take advantage of this and yeah sub accounts is coming really soon to to many apps and TV

yeah 100% um sub accounts are a great call out I know that the team is working as as fast as they can, as far as they can to make sure that we have all of that supported. We recently supported base pay, which is really great, which is what I wanted to show as well with Dylan's mini app specifically. If we go to wallet and just click base pay, like this is the quickest way for you to be able to make an onchain payment. It's a very minimal code that was required to get this up and running. Literally just a recipient amount.

So, it's the easiest thing. And then of course we have like a mini kit example to get it all working as well. So transactions in your base app should be gasless like the just to jump into that part of talking about transactions. Now transactions in a mini app like a gold standard mini app for me are gasless. So we're using Pay Master.

They are connected to my correct wallet. So I don't have to do anything at all to like switch wallets because you are just using the users connected wallet. And then on top of all of that, they should just be like they should be batched. There shouldn't be any two-part transactions. I shouldn't have to sign and then do a transaction.

No, it should all be part of the It should be one seamless like one click. I'm I'll show you guys what that looks like. I'll have to send poor Dylan. I keep flooding his wallet with 10 cents. I don't know.

I'm sure he doesn't mind.

He'll be retiring off my 10 cents once I hit base pay. Well, one thing before I before I send it over, you can see here that it's free. So I don't have to it's I'm not paying anything to do this transaction. It's already done. It's already gasless and everything.

And um that's it. Payment successful. That's it. That was super easy. Consider like consider that the gold standing for transactions.

Do you mind sharing the link to this mini app real quick? Uh or Dylan, since you're here, Dylan, do you mind sharing the pe the people want access to this?

And it's a great debugger. Yeah, it's amazing.

Yeah,

it's been really helpful. I mean, Dylan's an amazing developer and so is Mo and the engineering team working on mini apps, of course, are working so hard for everybody to make sure that we have par. We know we are now very close. I think this is the week that we're moving towards the end of we are going to be completely in par with Farcaster, which is amazing for all of us. Super grateful for all the developers and all their patience about this.

But yeah, being able to see like what works in the base app. Of course, we have it in our docs as well. But this is also a really great way to see like to debug for you guys. How does it like what does it look like? This little button down here that I think you guys can see is Aruter.

So, Aruter is a way for Arut is a tool and I have to give a massive shout out to Lemon because he's the one that put me onto this. Aruto is a way for you to be able to see the console on your mobile. So I can make console.logs and then also see it on my mobile. I think like all mini app developers if you have any issues anything like that there is of course in our docs in the debugging guide it is one of the top links where you can just click on it and say like mobile debugging there's code you can copy to get a router running.

So there's very like it's all there to set it up. There's a whole guide and everything. I strongly suggest if you're stuck check it out. I really love Aruter. It's been really great.

And what I was doing before I got sidetracked is just sharing this masterpiece.

We got it. Dylan Dylan's in the live. Yeah. Yeah. Dylan's in the live chat.

He's here. I think uh one thing I want to so recap and like ask you next steps, right? So today we talked about app architecture. We talked about mobile first experiences,

converting existing web applications to mini apps, right? It's really just two, three files, right? Your manifest, your embed file, and and your layout if you're using Nex.js, and then rendering the frame. We talked about wallets and authentication, sharing, you know, the only thing.

Yeah. Like what what else would you want to talk about? I mean, or should we open it up for questions from the audience? I think like one thing I'd like to give a bit of a shout out to is there will be there will be a way for mini app devs to be rewarded by base.

Oh

yeah, let's talk about it.

Yeah, let's let's go there. And it's really not going to be extra work that you guys have to do at all. We will have basdev. Basdev is going to be base tool like tooling for mini apps data. So really quickly as you're doing this, people are like, "What is this?

Another site?" So it looks like you are showing us a sort of builder version or the builder entry point.

Mhm.

Right. And this is like a gateway to base. This is to how do I see the pulse of my application? How do I see usage? How do I see the metrics around my mini app?

Is this is this correct? like what what am I looking at and and how does this link to me earning and things like that?

Yeah. Well, earning I'm going to there will be some more information about that'll be a big announcement for that. But what you're really what you're looking at is that there will be so we have all the metrics everything that you need to track growth to track user retention to talk about and I'll show my mobile again to show you guys but also like where is your mini app being opened all of this data to for you developers to be able to take it and then build based off like maybe mini app maybe your mini app is being shared in DMs quite a lot maybe it's something like really fun that friends do together how can Can I use that data point to better my product or my messaging?

Like

using data to be able to make help me make like better product decisions

is such an unlock

and it shouldn't just be like we should be looking at like a lot of contextual data to be able to move forward with building richer experiences and mini apps. And what I have on my screen is that all your mini apps that you can actually import all your mini apps. All you would need to do is at the top level. So this will not affect anything to do with how your mini app is rendered in forecaster is have base have a base builder key and your app URL. So I would just copy and paste this into my manifest and then yep that's it.

I would bring my mini app URL here. I would import

and then would you resign it? Would you resign your manifest with that uh parameter like that property?

Yes. I would not necessarily signed but yeah.

Okay. like the the manifest. Yeah, the manifest

the manifest won't be authorized if this doesn't exist. If that makes sense.

Gotcha.

So, it's not I don't want to say like resign it because I'm not changing the author.

If that makes Yeah.

Yeah.

And I want to and I I really want to make that clear cuz there are a lot of like mini apps of that need to have like this is just for you. So, anything that doesn't have like that wallet address or the associated account, it's not going to work.

It's easy. Sounds easy enough.

Yeah. Um, but yeah, this is all available and we really want to make sure like we're we're super hyped. App dev tooling has been our number one request.

Mhm. And we're delivering.

Yeah, we're delivering delivering as fast as we can to get it out there to you guys to build the best mini app experiences that you can.

All right.

Do you want to go through what we're going to be talking about for the rest of the week?

Yes. Okay. Thank you guys for coming. This has been uh mini apps 101. Share this with your friends and builders.

Uh if they want to just get the gist of what TBA is, you know, what are mini apps, why they should be building them, why it's, you know, and how it's so easy. This is definitely something you want to share out. Thank you for coming for the rest of the week. This is going to be the gold standard week. We want to help you to build really awesome milling apps, right?

Improve the quality, right? make your apps lovable, sharable. Um, and so tomorrow we are going to be talking about the user experience in many apps, right? We're going to talk about onboarding, more about wallets. Um, and then we have a special question of the day as well that we want you guys to answer.

And then on Thursday, we're going to talk more about building social. This is honestly the vir viral the viral the the viral. Okay? You want your you want your ass to go viral, right? you want to come in on Thursday.

So, we're going to talk about building social, right? Making sure your app is sharable and things like that. And then on Friday, we're going to be crushing bugs, okay? It's going to be debugging. It's going to be we're going to talk a little bit more about BAV.

So, we're going to have some more notes on that. You guys just got some alpha. All right? Don't tell anyone. All right?

But you guys just got a sneak peek to what's going to be announced and and talked to a lot more and that what we're going to build on. So, can't wait to see you guys for the rest of the week. And then the next week we're going to be talking about vibe coding and vibe coding mini apps and we're talking special guests. We're going to have you know AI tool you know creators coming in giving you know best practices helping you build really good prompts like it's going to be epic. So if you have friends that you you know who are developers and you want to get them in on building mini apps invite them in this week.

Invite and definitely invite them next week. next week is gonna be really good for creators, designers, product people who have an eye of uh for design and don't really know how to code but want to build a mini app. So, thank you for that.

I even like I would even just shout out like anyone should come honestly like we are all moving.

AI is our baseline internally. That's what we believe at Bass. So, if you're a developer, yeah, come come and learn how to how to best use AI to build your mini apps.

Yes.

But thanks so much for everyone coming. Thank you so much for building on base. What is the question of the day, Pat? Can you remind me?

Yes. The question of the day today um is why are you building a mini app and what do you hope it achieves? We got a couple good responses in the chat. If you guys, you know, don't have an answer now because I know probably another 300 people joined in. Comment below uh maybe quote the live stream and then answer the question, right?

Why are you building a mini app and and what does it do? What's the what's the purpose? So,

and tag me, guys. I want to see the answers.

Yes.

Thank you so much. Thanks everyone. Bye.

All right. Bye.

Automatic transcript — names and jargon may be misspelled.