Transcript
Translated into English:
Yesterday I had water damage. I lost 80% of my material goods in two hours and it was the best thing that could happen to me. I took my shower, put on my best suit, and headed to my meeting. Result: a signed contract for 150k.
Hello everyone, I hope you are doing well. Welcome to this new video. Today I'm going to do a crash test comparing two applications: Softr and Lovable.
The project is simple: I'm going to try to vibe-code exactly the same application with both tools and we'll compare. This past year everyone has been talking about vibe-coding. We get the feeling that with a simple prompt, we can create a functional app in minutes.
In reality, it's not quite that simple. That's why my goal today is to share a method for you to succeed in vibe-coding your first application. First, I'll redefine what vibe-coding is and the philosophy behind it.
Then I will vibe-code the exact same application on Lovable and Softr. I've chosen to vibe-code a bullshit LinkedIn post generator. It's going to be fun.
To make it more professional and concrete, we will go as far as creating a tool for creating, tracking, and scheduling LinkedIn posts that could be useful for any marketing team. This will allow us to compare Softr to Lovable.
This video is made in collaboration with Softr. I thank them for trusting me. Softr is an application creation tool that initially allowed you to create interfaces, but today it goes much further.
They now integrate a database part and a workflow part that I haven't shown you yet. The addition of AI that allows you to vibe-code your own app is quite impressive.
If you want to test the Softr AI Co-Builder, you have 200 AI credits offered with my link in the description. Even if you are a beginner, if you know your needs, you will be surprised by the result.
[.blog-callout]
Note from Softr: A fantastic way to get started is to use the AI co-builder. You can simply prompt for the app you want, and it builds the pages, logic, and database schema for you instantly.
[.blog-callout]
So what exactly is vibe-coding? It is the act of expressing your needs in natural language. For example, "I want to create an app to manage and publish my LinkedIn content."
You give this to an AI which handles generating the code to create the app. Even if you only see a visual interface, there is code being generated behind it.
The issue with vibe-coding, where I saw limits until now, is that the dream can stop quickly. As soon as you want to make a small modification, you might break everything without knowing how to fix it.
How do you add a member management system? How do you charge for access? These things require a minimum of code. Connecting to other applications also has limits when you only use the chatbot.
For me, the best combo is vibe-code + code. But that's hard if you don't know how to code. This is where Softr is different. With Softr, you aren't really vibe-coding in the traditional sense because it creates a no-code app.
That changes everything. You use vibe-coding to create your POC or MVP to go fast, but you aren't dependent on the code. You can update your app because you move to the no-code interface of Softr.
You can modify the interface using a drag-and-drop system. It is the best of both worlds. It is the Vibe Code + No Code combo, which is a much more realistic promise for non-developers.
Now we are on the Softr interface. I'm going to paste my prompt to launch the production. It starts by asking me questions, which I like.
[.blog-callout]
Note from Softr: While you can start from scratch, you might also find inspiration in our App templates, such as this AI CRM template for managing your business contacts.
[.blog-callout]
It asks how the app should generate posts. I want it to use OpenAI via Softr Workflows so I can update the prompts later. I can even change the AI to Claude later via API if I want.
It asks how users will connect. I'll choose email. Then it asks about the navigation bar and the theme. I like the Bumble theme because it's cheerful.
It starts by generating the data structure. Starting with the data architecture is the base and it is very important. It creates a user table and a generations table.
It adds columns for the anecdote, the bullshit level, the angle, and the three generated posts. Then it moves on to the interfaces. It usually adds a form so the user can submit an anecdote.
Even if the AI doesn't get everything right the first time, we can modify everything. It finished the first pages. Now I'll try it live.
I can filter posts by bullshit level and angle. I'll try to generate one: "This morning I drank a coffee." I'll set the bullshit level to maximum and the angle to personal branding.
I noticed it didn't automatically trigger the workflow. I'll ask the AI to modify the action when the form is submitted to ensure it triggers the post-generation workflow.
In parallel, I'll do the same on Lovable. Use a clear prompt. Describe the solution you want instead of just the interface. Focus on user needs.
For a V1, keep it to a simple MVP. Success doesn't just come from the initial prompt but from a series of iterations. With Softr, you can iterate with AI or by no-coding manually.
[.blog-callout]
Note from Softr: To keep your logic and data in one place, we recommend using Softr Databases. It’s the native way to manage your app's information without needing external tools.
[.blog-callout]
It's important to specify what should not be done. I also ask the AI to explain what it understood before it starts building to make sure we are going in the right direction.
Back to Softr. I need to go to the Softr Workflows section to create the logic. It's a classic no-code automation tool. If you've used email marketing tools, you'll recognize this.
I set the trigger for when a new record is added. I modify the button action in the app to trigger this specific workflow. I can even add a "wait screen" while the AI works.
I'll use the AI block in the workflow and select Claude as the model. I paste my prompt and test it. It works and generates a post.
Modifying the interface in Softr is so simple. It's no-code, so changing colors or moving a navbar takes three seconds. On Lovable, it's different.
Lovable's UI is very clean, but everything looks a bit the same. I can tell when an app is generated by AI. However, there is no automatic client portal like in Softr.
In Softr, I am logged in and can see the history of only the posts I generated. I can set this up in seconds. Managing members is much easier here.
[.blog-callout]
Note from Softr: If you're building a tool for your team, Softr is perfect for creating a company intranet where everyone has their own secure access and history.
[.blog-callout]
I'll add a database for an editorial calendar. I want a button on the generated posts to add them to the calendar. I'll use a Vibe-Coding block to visualize the generations.
[.blog-callout]
Note from Softr: When standard blocks don't fit your exact vision, the Vibe-Coding block allows you to prompt for a custom component that connects perfectly to your Softr Databases.
[.blog-callout]
I'm impressed. The AI created a custom block for this need. Now I'll add a new page with a calendar view to see all the scheduled posts.
It’s a great balance. You get a quick V1 from the AI, then you adjust everything with no-code. I use this all the time for my clients now.
To recap: vibe-coding is powerful for POCs. But if you aren't a developer, you will hit limits with code-heavy tools. You might encounter bugs you can't fix.
For professional environments, Softr is a more robust solution. You stay in control. You get the speed of vibe-coding with the safety of no-code.
[.blog-callout]
Note from Softr: Softr is ideal for various portals. Whether it's for project management or a CRM, you can build it quickly and safely.
[.blog-callout]
By the way, regardless of the plan you are on, Softr now allows for unlimited published apps. Go ahead and test the AI credits. I'm excited to see what you create.
