Live data from Hacker News

Create JavaScript, CSS Interactions With Zero Lines of Code

interactions.webflow.com

51–60 of 63 posts

Re: Create JavaScript, CSS Interactions With Zero Lines of Code

#52

The most important thing to keep in mind is this is for designers not coders -- I haven't looked at this deeply enough to know if it is good yet, but my guess is if you read hacker news comments it isn't for you because, well, you probably code=). Yes, these sorts of editors often create horrible leaky abstractions. Yes, these editors often confuse product folks into thinking that coding isn't necessary or important…

Actually I think Webflow can be a useful tool for if you're a developer who wants to learn how to design a prototype. I struggle with visualizing a new site without a mockup or style tile for reference. Webflow's UI is intuitive - everything you do has immediate visual feedback and directly translates into clean CSS/HTML. The previews of media queries affecting content is nice too. So it's very easy to reverse engineer how to make a good design, the same way you would reverse engineer some source code.

But with that said, I am not a paying customer. When I need to make a site then I just sign up for a free trial and export the code to continue the project. Their individual plan doesn't really make sense for me and I think it's too expensive.

Re: Create JavaScript, CSS Interactions With Zero Lines of Code

#55

Earlier quoted context omitted.

I'm the founder and CEO of Webflow, and I can't agree enough with your statement that code is not the hard part. That's why we're trying to create tools for designers to help them focus on the hard parts (content, usability, etc). 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…

I absolutely agree with all of you say -- which is why "without code" is misleading / unhelpful. A better tagline for the web interactions site would be: "Don't code website interactions; design them."

As long as "without code" is the copy that converts better, then it doesn't matter.

Re: Create JavaScript, CSS Interactions With Zero Lines of Code

#56
post #5

Let me preface this by saying: I have the upmost respect for the Webflow developers and designers...they've created a highly-functional web app with the purpose of enabling creators...the process to make such a full-featured web-browser product with such a range of capability is astounding. That said, I disagree with the implication that Webflow, and similar products, solve the problems of code, e.g., the phrase "Do…

I'm the founder and CEO of Webflow, and I can't agree enough with your statement that code is not the hard part. That's why we're trying to create tools for designers to help them focus on the hard parts (content, usability, etc). 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…

I agree. In the end, the user doesn't care about how the site is build just like a driver doesn't care how a car works.

Re: Create JavaScript, CSS Interactions With Zero Lines of Code

#57
post #17
post #13

Earlier quoted context omitted.

None of the scroll animations work in Firefox either. Not just touch based devices. Didn't leave a very good impression on me.

Kyle from Webflow here. Are you on the latest version of Firefox (28.0)? The scrolling animations are working for us.

FF28 Fedora, the animations work but scrolling is choppy (like a slide show).

Re: Create JavaScript, CSS Interactions With Zero Lines of Code

#60
Sure it demos well, but it's closed-source. Vendor lock-in sucks, full stop. And the time investment spent learning it won't pay off bc those skills won't carry over to the vast majority of other future projects that don't use it.

Building a site on bootstrap (from source, ie integrating bootstrap's less files as dependencies in your webapp via grunt and bower) is defensible; becoming entirely dependent on the capabilities of something like webflow, imho, is not.

I suppose if you're a designer in a hurry to build a pretty, throwaway site (eg a microsite for an event) then this might be worth your while. But if you're building something for the enterprise, anything you or your team might want to maintain and extend, I think it represents an unacceptable level of knowledge debt, to rely on site-generating tools like this.

YMMV of course. My views are skewed towards the UI architecture needs of a multi-million-dollar global company.

/$.02

Post reply on HN