Transcript
an app without touching any code, and I jumped to Bolt.new as the answer. Then they said, what about Lovable, and I had to admit I'd never used it before. So here we are. Same prompt, both tools side by side. And look, part of this is just genuinely fun to watch, but I also want to hold these tools to a higher standard than most, because the goal isn't to build something that looks like an app. It's to build something that actually is one. Let's find out which one gets there. All right, so here we are, both websites side by side. Lovable on the left, Bolt on the right. I'm giving them both the same prompt at the same time. What's oddly interesting here is look how similar these landing pages are when you go to them for the first time. You have the prompt window or chat window right in the middle, the option to start building something right away. And when I click to send that in on either one, we get very similar login attempts or registering attempts as well. So I'm going to go ahead and sign up for both of these, and then we'll jump back in with sending this prompt to them. All right, so here we are, Lovable on the left, Bolt on the right. I'm signed into fresh new free plan accounts, and I'm going to send in the same prompt at the same time. Here we go. Bolt is often running creating a database schema with migrations. And where I left off with Lovable was it's asking me about enabling cloud, complete backend and AI models out of the box. I suppose I should allow that. I don't know if that gives it an unfair advantage over Bolt. I'm imagining Bolt's doing that already. Add database authentication, storage and edge functions to your apps with built-in full stack hosting that scales automatically. Being that Bolt is doing a database and all that stuff, I'm going to enable this. I'm going to say allow. I have 4.10 credits remaining, it says. I'll build a warm workshop inspired DIY form with all the categories. Okay. V1 features landing with categories posts. Let's start to enable by enabling the backend with often database. Now let me create the database schema. Okay. So they both seem to start on the database. We'll cut back in once these have made significant progress worth sharing with you all. All right. Checking back in after about, I don't know, two to three minutes, Bolt seems to be done already. Whereas Lovable created a database schema and it's still working on building the design system and UI on the left hand side there. In terms of speed at which these tools take the prompt and get to a final product or a final result that you can start using, Bolt's got the slight edge there and win in that column. As I'm saying that Lovable looks like it finished. So it was shortly after that within a minute or two of Bolt finishing, we have Lovable done. Let's take a moment and look at them full screen. Whoa, I got another pop up from Lovable here. Team up for free. I don't have any friends to team up with. Publish the project, your project name, lovable.app. Let's give Lovable a run and see what it came out with. So I'm going to go full screen with Lovable here. And we're going to see there is a sign in capability. I'm going to say test at example.com. Give it a password. We're going to say Clarkview. Okay, nice and fast and snappy. We have different categories. It's the fix it forum share tips, tricks and solutions for DIY home repair. Learn from your fellow homeowners and help others fix it. Right. Okay, then you can browse by category whether it's plumbing, electrical flooring, general carpentry and painting. Recent posts, we have no posts yet. Be the first to share. Let's let's create it. Let's if I click on one, what happens? Okay, it just goes to things that are filed in. Let's create a new post. I'm going to choose plumbing. And we're going to say how to defrost a frozen pipe. This actually happened to me recently. I get an extension cord and a hair dryer, plug the extension cord in and bring it to bring it to the area where you suspect your pipes are frozen. Then plug in the hair dryer. I'm taking this example way too long, but you're going to stick with me for this folks, the hair dryer into the extension cord and turn it on. After that, make sure your hair dryer is in heat mode. And then point it at the frozen pipe or 1010 to 15 minutes. Check if water is flowing afterwards. And if not, repeat, publish posts. See what happens. Oh, fancy styling by Clarkio one, you post a comment. Oh my this helps so much. Thank you. Alright, my comment is there. If we go back to the fix it forum home, we can see there's one post under plumbing now. And there, there it is under recent posts as well. So that's really cool. That works great. We sign out, sign in, maybe register a new account, frozen pipe, frozen, sign up. I'm in, I can see got my water running in no time. Right? So we have another user now frozen pipe, comment added little toast notifications going on here. Look at that. Very nice. Very, very complete. I like it. I wonder security wise and, and just practicality wise, like how well this would hold up on our, when it's really deployed. Pretty cool. I like the style of it too. Let's kind of evaluate that right. In the sense of like, it kind of gives me a feel for those of us that are based in the U S of a company like home Depot, the orange and white kind of theme with the little wrench and stuff like that going on to show that it's a DIY exit forum type of thing. So very cool, pretty complete in the sense of what the prompt gave it as a homepage with category grid and recent posts and off you can create posts. You can comment and the design Amber accents, DM serif display headings. Don't know what that means. I guess the font and smooth card animations, lovable cloud powers, the database off in real time data, email auto confirm is enabled so you can test immediately. Very cool. And then it gives you like little follow-up possible prompts. You could say test the full flow at post search at post upvotes, add user profiles, stuff like that. Right. We're going to leave it there for now. Apparently I used up three of my 4.10 free credits remaining for today. So maybe tomorrow I could build something else that's lovable. And that's what it did with the prompt of building a DIY forum. All right. Next up, we're going to check out Bolt and see how it compares. Okay. Here we have Bolt and we're going to sign up. Cool. All right. We're signed up. All right. In terms of the design of this, right? Visually similar functionality, right? We have all posts. We can see all the posts in various categories in this case, all categories, but then you can filter by different DIY subject matters, right? General HVAC painting and all that. Uh, it didn't quite pick up the name. It was welcomed comma blank. I'm guessing it wants a name there. Uh, so that got messed up a little bit in terms of overall style and look and feel I'm given lovable plus one on that. I think this, I think this one by Bolt is not bad. And by no means would I have done a better job in either case. So let's make sure that's clear. But when you're comparing the two against each other, I think lovable has the win there in that regard. Now let's create a new posts. We're going to collect category of electrical says, uh, light switch not working. If your light switch isn't working, try, try turning it off and on again. So there we go. We can, we add a comment to it. Um, the best, uh, electrical DIY advice, a little self-centered here in that regard. So now we go back to post. We can see there's nothing at the carpet under carpentry, but if we go electrical, we can see that that's there. If we go all categories, it's there functionality wise, all working great. Now it's now it's showing my name, my username in the top right hand corner. So it must've been a weird little bug at the beginning there. We sign out, let's create another account. We're going to say, uh, zap and zap at example.com. Don't let zap and Clark, you'll know, but they have the same password. I tried this and was lightly shocked by the results. Thanks. All right. Anyway, you get the idea, right? It's all working multiple users here. What if we try signing in with zap at example.com with the wrong password? See what happens. Ooh, invalid login credentials. Okay. Okay. Okay. In terms of what I'm able to do with the free tier on both platforms, lovable seems to like have a different approach to tokens and credits. They call it credits. Bolt calls it tokens. It looks like I get a lot more free access, free tokens with bolt than I do with lovable. Although it's somewhat comparable, at least I didn't use up a ton of them with this particular prompt here. In any case, uh, I have 13,000 daily tokens remaining daily, right? So I get a good allotment seems to be more like the number is larger, but how that relates to the actual usage rate for each platform and how they approach these tokens or credits. That is up for question that I need to dive in deeper and get more use out of both of these to really get a understanding of the difference between those two. So take that with a grain of salt. If you're trying to pick one over the other, based on that, the natural next step here for any user would be now I want to make this available to anybody else to start using it. I'm happy with what bolt or lovable has done. Let's see what the process is like in getting it published and in a production ready environment, if you will. So it looks like the similar way that lovable had it. We have our button in the top right-hand corner called publish. I'm going to click on that. What's running a security scan, one security issue detected. That's pretty cool bolt. All right, let's review this security issue. Security audit identifies vulnerabilities like missing role level, security, RLS policies, and insecure permissions. Use ask bolt to fix to apply recommended improvements. Okay. We have leaked password protection disabled. So if a base auth prevents the use of compromised passwords by checking against, have I been pwned.org, enable this feature to enhance security. Oh, bolt, can you fix it? Now, the interesting thing is if it's able to know about possible security issues, why doesn't it include that scan with the original prompt, with the process around the original prompt? That's one thing I'm wondering right now, just speaking out loud. I do like that it has that capability, but the overall experience would be better if it just naturally did that. And it can comment in the chat window here, like, hey, we noticed that the original implementation or the initial implementation lacked this security measure. We scanned it and here's the results of it, right? So it applied database migration. So that's good. And now removed unused indexes that weren't benefiting query performance. Again, this type of stuff I'm confused by, like, why didn't it do that first go around, you know, but in any case it optimized the role level security policies for performance by using select auth.uid pattern. Okay. Sounds good to me. Now it's actually publishing. I wonder like with new changes, if it would run a new security scan, that'd be interesting. Your site has been successfully published. You can view it at here at a custom domain or purchase one through bolt upgrade to bolt pro. Well, that's interesting to hear too, because I didn't know you could register domains through bolt. That's a nice feature. That's like the reason I'm bringing these things to light into your attention is if you are in this camp of this user from my community that asked this question, you're likely looking for like an all in one package that handles all this stuff for you. You're not having to run off to different places to figure that thing out, right? So in this case, you need a domain for your new app and idea that you wanted to build that you're going to publish to and have people go on their browsers to check out. I wonder if the ones that I already used, like archeo at example.com are still in there. Yes. Okay. So there we have it. It is published publicly available. And by the time you're watching this, I may or may not still have this up and running. If it stays free, then sure. I'll keep it up and running up on bolts website. If not, then, uh, sorry, I'll take it down. So check it out while you can, if it is available, curious to see what you all try and do with this app. All right. That said, let's try publishing the lovable version of it. So we're going to click publish in the top right hand corner as well. Let's see. Does it do any security checking? No, it just immediately already has that sub domain on lovable.apps website available. So we can click on that and go continue. Yes. I want it to be public. Do we want social images? Okay. This is kind of cool that it offers this, that we didn't get from bolt. If you wanted to change what the, the tab title will show and the icon, you can upload an image for that, write a description for, especially for SEO purposes. If you want this website to be more discoverable by search engines and social images, if you'd like to, when people are sharing things from your website on social websites, I like that a lot. And it shows you a preview of that too, right here. Very cool. Nice job. Lovable on that. Anyone with the link, you can, I guess, lock this down. A website info missing, ready to publish. Okay. So now we're going to publish. Can I change this? DIY wisdom hub. I'm okay with that. We'll just leave it like that. What it came up with. Publish that just like that. This is taking a little bit longer than what we saw with bolt. And there we go. We have it ready and available under this URL. I'm going to click on view app and it's up and running. And here's the thing. It is publicly available without signing in. You can read this form, which is kind of cool to see. It's kind of like Reddit or other form-based style message board websites. And I like it. Let's see if we can sign back in. What email did I use for this? I forget. Tests at example.com, I think. Invalid login credentials. There we go. Oh, that worked. Okay. Who am I signed in as? I think I'm at Clarkio one. Okay, cool. So I was able to sign back in, sign out. Everything's good to go. So I don't know that I feel there's a clear winner among the two. I would say design-wise, I like the design that lovable came up with better than the one that bolt came up with. I also like that lovable makes it to where you can read the site without being logged in. Whereas bolt, you have to be logged in first in order to even read the site for the purposes of this, right? Like it's, it's meant to be a public forum that people can share ideas and learn from for DIY projects at home. Lovable picked up on that, right? They recognize the context that this is going to be used within and the purpose of it, and therefore made it, built it out in a way that'll enable that access like that. That's typical on the web. In terms of the overall functionality based on the prompt that we gave and the expectations of what we want, both of them checked all the boxes there. You can register, you can sign in, sign out, you can add categories at post, you can comment on posts. And the only thing I didn't add this, but it, you know, maybe somebody wants to delete their comment or delete a post, something like that. Edit a post that they did see which ones that they did have a profile, keep track of what they've shared in the past, that type of thing. But again, this was all from a vibe code type prompt, right? One shot prompt. And I think they both did a great job with the minimal amount of information that they were given. So that's even there in that regard, there's no clear winner in one doing better than the other in that regard. All right. So I've been approaching this from the sense of somebody that's not really interested in getting into the weeds of the coding and the stuff behind the scenes that make the app actually run. If you want to though, what's nice that I've noticed exploring both platforms is they give you access to the code, to the database capabilities, like exploring the tables and authentication and analytics. There's a lot of really helpful features that are available directly on each platform that are very comparable, almost one-to-one, I would say. So if you're interested in that type of stuff, let me know in the comments below, and I can do a deeper dive into that stuff for those of you that are more technical and want to get into the weeds of using these types of platforms for building out apps very quickly. But back to the standpoint of somebody that's not interested in that, you're also probably interested in the pricing capabilities of it. From the free tier standpoint, as I mentioned earlier, I'm able to do quite a bit already with just the free access that I'm given for a new account on both platforms, with both using the term tokens and Lovable using the term credits. Bolt, they give you 1 million monthly tokens to use with an extra set of tokens that you get for signing up and giving more information about like whether you're an engineer and that type of thing. And in the sense of how many tokens I've used for that particular prompt, I used 300,000 tokens out of my 1 million tokens for this app alone. When it comes to Lovable, they gave me five free daily credits and I used about four of those credits. So it's a little bit kind of confusing and like hard to compare one for one there. It seems like if you kind of normalize both, they're pretty close in terms of like how much token usage or credit usage I just went through with building out this DIY forum application. If I wanted to upgrade, we can see that both of them offer a monthly plan at 25 US dollars per month. So it's very comparable in price, but in terms of like what you're getting, it's hard to compare because I'm getting 10 million tokens monthly with Bolt, but I'm getting 100 credits monthly with Lovable. So I'm not quite sure which one really gets the advantage there and what you're getting more bang for your buck with. They're very comparable and they're very competitive, I would say. Whichever one you choose, you're likely going to be successful. And I don't really feel there's a clear winner here. Do we feel there's a clear winner? I think from a design perspective, based on that limited prompt, I give the slight edge to Lovable. So really quick, I did a little bit more digging on Lovable's side of things because I wanted to see if they had some security feature built into it as well, like Bolt. And when you click in the menu options here, you can see security is one of those options. And when you click on that, oops. And when you click on that, it brings you to this view. And it looks like I can do an advanced view. What's that advanced view? Project dependencies. So it looks at the dependencies that I have or any of those with vulnerabilities. Can I update it? It too had a leaked password protection disabled as well. And it has the capability of getting that fixed by sending that in the prompt in addition to, oh, and it found some more. Okay. So really interesting. They both have security capabilities. If you're paying attention to that and very concerned about that type of thing as a non-technical user, definitely something you should be aware of, but this might not make a lot of sense to you, what's being shown here. So you likely are going to click on these things and say, hey, just go fix this for me, Lovable or Bolt. But I like that there's a dedicated view in Lovable and I'm kind of giving the slight edge back now from Bolt to Lovable in that regard, because it has this scanning capabilities built into what it made. So very cool to see and very interesting. And it looks like you can just send that into the prompt basically and say, review. It's still scanning right now, but you get the idea. I can expand on this, learn more about what it detected, and I could choose to ignore the issue if I'd like, or ask Lovable to analyze and fix that finding. So there you have it. It looks like it was already fixing that one. From the standpoint of a regular user, non-technical background, probably going to go the Bolt route, just let Bolt do its thing and scan things automatically for you. Whereas Lovable, you have to go into the security view to get access to that and be thinking about it to do it in the first place. So I give a plus one on that to Bolt still. And then in terms of the overall functionality, it's even Stevens there. I don't see one outperforming the other. The slight edge goes to Lovable there, but I'm not going to give it a full point in the sense that it has the true idea around what a form should be that it can be publicly accessible, whether you're logged in or not. Right. So there is that aspect of it on that note, though. What do you all think? Who do you feel is the clear winner? I think it's slightly Lovable and who else? What other platforms that I missed that are like Lovable and Bolt that are competitors that we should put up against the winner of this one? Let me know in the comments below. We'll get the next video rolling on doing just that. That does it for this video. If you got value out of it, be sure to like it down below and share with somebody who put it to use. And if you made it this far, subscribe to the channel so you don't miss out on upcoming videos. Thanks for watching and happy safe coding, everyone.
