Webflow has announced View Source, a live show starting 27 October that gives a first proper look at Source, which builds sites three ways: on the visual canvas, with the Source agent, or in code. Sam is excited the community feel might be back but wants to know the price. Kabarza argues few people will build on a visual canvas any more, and Sam ends up defending Webflow.
Would you still build on a visual canvas, or hand it all to an agent?
Taken from Cmd+ AI Ep 71, our weekly live show covering AI, design and dev. Catch us live every Friday and join in the banter.
—
TIMESTAMPS:
00:00 Webflow's View Source show
01:02 Source: canvas, agent and code
01:33 How will Source be priced?
03:11 Are visual editors over?
05:16 Why people still need the canvas
06:24 "I'm the one defending Webflow?"
07:08 Is the community back?
07:42 Outro
—
Unlock the full potential of your online presence with Kabarza and Samuel—experts in web design and development (respectively), powered by cutting-edge AI solutions. We blend creative design with advanced tech to deliver smart, high-impact websites that stand out. Ready to elevate your business? Contact us today and see what AI-driven innovation can do for you!
LINKS & RESOURCES:
Website: https://cmdaishow.com
Check out Kabarza's amazing work: https://kabarza.com
Visit Samuel's website for more: https://samuelgregory.co.uk
📷 Follow on Instagram: https://www.instagram.com/cmdaishow
—
HASHTAGS:
#Webflow #NoCode #WebDesign #AIAgents #WebDev
#ai #podcast #aidesign #aidevelopment #vibecoding #webdesign #webdevelopment #ainews #webnews #designnews #devnews
Transcript
I don't see myself or many people be building using a visual editor anymore. How is it that I'm the one defending web flow? Command AI. So, we're about to get our first glimpse of Web Flow source and the community might be back. So, Web Flow showed us this. Build for the web at aentic speed with your codebase as the source of truth. This is source. Watch it live. View Source episode 1, October 27th. So that's next Tuesday at 9:00 a.m. Pacific, 12:00 p.m. Eastern. Join us. Timothy Ricks, Matthew Munger, and Catherine, I don't know how to say that name. Really sorry, Catherine. So, I'm pretty excited about this and I think it means more to the community than we think it does. Uh, we'll show you live and unscripted what we're building with Source by Web Flow. So hopefully there's going to be a load of demos actually using web flow and these are two technical people as well. Source working on a real Astro or Nex.js project built with three in three ways with the source agent on the visual canvas and in [music] code. The worry is that the visual canvas has taken a back step but the fact that you can can you build an entire site on the visual canvas that's going to be the the thing. I have comments on that. This is the first time they've done something like this in a long long time. And I think I'm genuinely excited about it. My only negative is I think everyone's anxious about the price. I think we just we want to know how much all this magic's going to cost, if anything at all. So, yeah, I'm on the edge of my seat about that. Maybe they're going to release the price. But anyway, thoughts, opinions? I think you just nailed it. the price and how how they are going to charge you. It's not just is it going to be expensive or not. We know Web Flow is not the cheapest tool but you know compared to Framer again they're not too expensive but compared to today's market like you get yourself a claw max subscription if you are doing anything serious you have that right now the question becomes how will web flow charge you is it going to be per website that you host on their cloud infra infrastructure and then maybe use their agents because they specific specifically mentioned they give you three ways to do things. One is you do it yourself on the canvas. Another one I'll I'll comment on that. Uh another way is through their agent which I assume is going to cost just like how it is with framer and how it is uh you know with pretty much every other tool out there. And then another one is code which is technically just you know you can do this with claw code. I'm most curious about knowing how can I do the work with cloud code in the way that I like doing it and then how can source add some value for [clears throat] me with the custom views maybe with the the access with teammates and things like this maybe even the canvas and now my comment what I mentioned about the canvas I don't see myself or many people be building using a visual editor anymore and the reason for that I for a long time I thought that that's how I wanted to do stuff. But I started doing it with stacking and I noticed the biggest issue is as these builds get more complex, you will no longer know how to do stuff, right? You might know that okay what systems is being used for the styling and so on but isn't it better if you let the agent to take care of that side of thing and you kind of like orchestrate the bigger picture instead of like trying like conceptually it's easy to think and understand well I have a heading it's too small let's make it bigger which way is easier to ask the agent to do it or just literally drag it and make it bigger. Of course, dragging it and making it bigger is just much more uh joyful as well. Like I want to do it, but I'm a bit reserved there. I'm pretty sure you cannot do this reliably because you don't know how everything was built unless there will be a layer built that allows you to do these kind of things and then that can be translated into something for the agent to take care of and be like this user made this bigger let's find the most scalable way to do this across the website or just here so I can see a lot of workflows can happen with this type of like essentially just prompts. But at the end of the day, I think the future of the web is to build these experiences with prompts. Again, another thing to be really um excited about is the controls that you can, you know, ask the agent to make. So, it's not the canvas controls like the standard ones, but actually the specific controls that you make for whatever you're making. So, I want to see those and I'm excited about them. I disagree because We see it in our comments. We see it in the passion behind Timothy Ricks that we there are still people, we know this. There are still people who can't uh what's the word? They can't process the idea of what's happening with code and files. They need the visual. You know, you do this because you know now and it if it wasn't for the if it wasn't for Web Flow giving you the foundation to understand this your jump to aentic coding is much much smaller. But you got to go right back to your day one of using Web Flow and how simple visual how it's so easy to understand. The first website you ever built probably was a mess, but let's be honest, you knew what was happening. It you were in you were in control. And there's just going to be so many people who need that. But this will only make sense if the price is right. If it's free, we can drag and drop and build with Web Flow for free. I think that will be heavily used. I just don't think it's fair to say that this is how we're building now and everyone should just accept it. There in lies the magic that source is meant to bring. This interoperability, this like you use your agent, you use the, you know, we want that smooth transition. And I have to say I started laughing. How is it that I'm the one defending web flow? I'm not like against any parts of the source. I'm just saying like realistically I won't be using the on canvas direct editor realistically. Maybe for content like I still find it just much easier to just type in the content or maybe you know all the eyebrows for the eyebrows that the the agent has you can just click them and delete them. you know, there there is joy in just pressing the delete there. But either way, to remain positive, I I'm looking forward to this stream and I hope that it's a continuation of or sorry, not a continuation, a revi revision of the Web Flow community because this this looks great and I hope it doesn't turn into a frigin business marketing. Hey, we've got the our CRO. No, no, no. What is it called? What do they call AIO or whatever they call it? I I want it to remain community focused, but that's for episode two, three, and four to decide for us. But yeah, for the first one, the community is uh is back. This is part of a larger conversation on my show, Command AI, which we stream live every single week. We discuss the news and all things related to AI in the world of design and web. Catch us next week and join in the banter. Command AI.