As I utilize the vibe-coding block and also experiment with vibe-coding outside of Softr, I realize - why couldn’t EVERY Softr block have a vibe-coding option? That is, you start with the rigid definition of the block, using its many options, but then you tweak it further with vibe-coding. With guardrails, of course. If the vibe-coding changes detail the block, there could be an option to “reset the block back to factory settings”, so to speak. This would solve the issue of stretching the block’s functionality beyond what it offers out of the box by Softr. I am sure every one of us has a wish-list of what a list block could have or do.
I figured, if Softr can handle integrating the vibe-coding block with the data sources, fundamentally, at that point the block becomes analogous to a Softr list block. So, if further code manipulation is accessible via vibe-coding changes, this might as well work on a regular block, too.
I’d be curious to hear what the Community might think of this, as well as what Softr product dev might think of this, too.
****
Taking it to the next level, could there be a Softr extension built for Cursor, where the components could be vibe-coded in a full-fledged IDE (with rules, skills, etc…) and then brought into Softr as a block? Again, I see some limitations, like accessing the data sources defined in Softr. But still, at least the design of the UX/UI could be accomplished in Cursor (with its many features) and then brought into Softr as a block and then the data sources and further data-related vibe-coding changes could be done locally in Softr.
This is a really thoughtful proposal — and yes, you’re essentially describing vibe-coding as an extension layer on top of existing Softr blocks, rather than a separate block.
Conceptually, this is very aligned with where Softr is heading: starting from a native block (List, Calendar, Table, etc.), then allowing AI-assisted customization and extension with guardrails, plus a way to reset back to the default block behavior, so these are in our plans.
Thanks for sharing such a clear vision — this is a great example of where AI-assisted building can go beyond today’s no-code limits.
This would be a fantastic addition as there’s lots of small changes I’d like to make to the appearance of blocks and adding the vibe coding layer on top of pre existing options might help with most of these
The way this thread got started was the idea of ADDING AI vibe-coding to the standard blocks, not REPLACING them. This way, we could start with the standard block functionality, but then adjust/improve them through vibe coding, where the current styling or action settings fall short. Let’s be honest, the styling settings on standard blocks are sometimes limiting. On the other hand, vibe-coding, does not always produce the desired results either. But what it does do is it gives access to the code it generated, so that we can fine-tune it manually. That’s very useful.
The other thing is that Guillaume comes out with a lot of content showing off incredible vibe-coded blocks that do a lot and look nice and many of us are wondering: “how did he do that?” The iterative vibe-coding process that went into creating them isn’t always shared.
It would be great for Softr to build a “marketplace” of vibe-coded blocks, where both Softr resources and the user community could share their incredible vibe-coded block creations, that other users would be able to pull from and install into their apps and use as a starting point and then maybe vibe-code further, as needed.
This would solve the issue of stretching the block’s functionality beyond what it offers out of the box by Softr. I am sure every one of us has a wish-list of what a list block could have or do.