I love what Bret Victor says about this in his Magic Ink paper [1]. Replace "information software" with "web applications" as you read it:
"I suggest that the design of information software should be approached initially and primarily as a graphic design project. The foremost concern should be appearance—what and how information is presented. The designer should ask: What is relevant information? What questions will the viewer ask? What situations will she want to compare? What decision is she trying to make? How can the data be presented most effectively? How can the visual vocabulary and techniques of graphic design be employed to direct the user’s eyes to the solution? The designer must start by considering what the software looks like, because the user is using it to learn, and she learns by looking at it."
The act of creating a solution IS the hard part, not tweaking CSS properties or knowing how to integrate Bootstrap components just right. All those things should just get out of the way and let creatives do the important work, without bogging down in the implementation details.
In case you're interested, I wrote a bit more about this on our blog a while ago: http://blog.webflow.com/designers-will-rule-the-web
A better tagline for the web interactions site would be: "Don't code website interactions; design them."
I am the developer of HiveMind (crudzilla.com), it is a web app platform designed with the aim of lowering technical barrier in mind.
My approach to the design of the product is to create something that people with moderate programming and web development skills can use to build high quality web apps. That means for instance being able to integrate the work of a more sophisticated developer with the ease of drag-n-drop and "fill in the blank" type workflows. But ultimately the end users still needs to know how to code.
The allure of eliminating the need for coding is one that has been around for a long time and continues to be attractive to businesses but it is a misguided approach that doesn't work.
I worked for an employer that peddles a product that claims to require no coding, instead you end up filling out forms until your fingers hurt because you are essentially coding in a convoluted manner.
again, no knock on the site, it looks like it's really well done, i'm just not sure that a series of complex controls solves the problem of web development any better than just learning how to code yourself.
It boils down to investment and return. If designers can build responsive sites faster and easier with great code output (see source code) using a WYSIWYG, then it makes more sense to invest in that versus learning how to write the same code. Front end devs use frameworks like Bootstrap and Foundation to cut development time. Webflow serves the same purpose, but all the framework components are made visual.
This visual abstraction makes it more accessible for more people just like these frameworks made web dev easier. There is always the possibility of people using Webflow and creating poorly-coded websites, but anyone trying to code can do the same.
Again, I'm sure your intent with this product is not "build every website out there," but I am concerned by those with a little knowledge and ambition using your site as the easy way out for making a website rather than taking the time to actually learn how to do all those things for themselves.
I imagine this tool is perfect for creating a beautiful landing page or similar. Obviously one isn't going to try and use it to build anything enterprise grade.
But there lots of jQuery plugins or css frameworks out there but they largely seem to have active user bases.
The audience here is people that feels comfortable doing stuff tweaking parameters on a dialog box, they don't care if the dialog box is actually a lazy evaluated reactive continuation or whatever as long as it does the job.
An abstraction layer for web technology is as relevant, revolutionary and useful as an abstraction layer for the CPU was on its time (in fact the most succesful companies did exactly this).
That said, I disagree with the implication that Webflow, and similar products, solve the problems of code, e.g., the phrase "Do xyz without writing a line of code". Knowledge of code does constrain non-developers, but in the end, that is not the hard part. To use a quick example: the mechanics of baking responsiveness into a new site from scratch is significantly easier than the conceptual process of "What information and features should be prominent, or excised, in the mobile view of our website?"...and in my opinion, that latter problem is something that people can get into without knowing how to write code.
So despite the technical strength of the Webflow product, I don't think that it makes things easier in the end. Instead of "code", a newbie has to learn a whole new interface, a whole new set of iconography/terms (used for buttons, subheads, etc.), and last but not least, a whole new set of quirks inherent to the Webflow program. And when they become experts at this, they have spent 50-90% of their cognitive ability mastering Webflow, and the remainder understanding the creative and technical process of web development.
At some point, isn't it just better to learn some code? Not 10 years worth, but something in between that and "0 lines of code". I've used Webflow, and I'll repeat again, it is an excellent web product in execution and design...but the problem it attempts to tackle is just too big, and the abstractions it offers may ended up hindering creators in the medium-to-long run.