Another fine example of how Chrome is the new IE6...
Show HN: Webflow - Design responsive websites visually
51–60 of 137 posts
Re: Show HN: Webflow - Design responsive websites visually
#52Working pretty good in FF Nightly though!
Re: Show HN: Webflow - Design responsive websites visually
#53Earlier quoted context omitted.
These limitations are all slowly disappearing as web standards are advancing fast to fill these gaps. I think soon we'll be able to give trusted web apps permission to read/write to our file systems and reach out to more OS-level interfaces that our browsers have access to. Web apps also offer advantages over native apps, like zero installation, universal compatibility regardless of OS, and the ability for publishers…
>universal compatibility regardless of OS The browser becomes the OS for web apps, and in this case Webflow only supports one OS, Chrome.
Re: Show HN: Webflow - Design responsive websites visually
#54Have you thought at all about price point? IMO I wouldn't try to enter the hosting space, at least not yet. That's not the value for me. I think you have a great product in the works just as a front-end development platform. If it works as described, I'd put money down for it today (customer validation, check).
Re: Show HN: Webflow - Design responsive websites visually
#55Co-founder here. My brother and I quit our jobs 7 months ago, and have been working on this day and night off of our savings since then. The CSS Playground is a preview of our CSS styling tools, and we'll be adding some of our other components (layout, adding new elements, code export) soon. Currently, it only works in Chrome, but we're working hard to add Firefox support.
Super awesome and very well done, just played with this for a couple minutes..love how you can choose the different platforms on the left and side and when you click on an element you can edit everything on the right hand side. How do you plan on monetizing this?
Re: Show HN: Webflow - Design responsive websites visually
#56A long time ago I built "squeeze page" manager which had an editor like this (it was simpler and more focused on content management). I sunk a lot of time into it. However, I ran into the same problem I bet you guys will run into: "the design tool chasm". On one end are simple tools for publishing on the web (Weebly and Wordpress) and on the other are professional tools (Photoshop and Sublime Text 2/Textmate). In between are tools that no-one really wants.
Basically, don't stop at the editor. Its a feature. Take a look at Unbounce or HubSpot for "marketing tool" inspiration and Weebly and Wordpress for "publishing tool" inspiration. Or, if you want to be used by professional designers, you'll need to go in a whole different direction (which is likely the one you are on now). Of course, if you have target customers that love this as is, their feedback vastly trumps mine. But never stop talking to your target customers (steal them from the big boys with your personal touch and solve their problems)! Good luck guys!
Re: Show HN: Webflow - Design responsive websites visually
#57This is really nice, but I just can't get too excited over web apps. Whether it's not having direct access to my source files, relying on the service to stay up (either from server or business issues), working when offline, not having access to OS-level services, the clunkiness and slowness compared to native, or the cognitive overhead of the app being inside another app, I think I'll always prefer desktop apps.
Or is it because of my negativity toward web apps and an appearance of ignorance on the state the art?
Re: Show HN: Webflow - Design responsive websites visually
#58Also this is probably first HN thread that everyone seem to like what they saw, no nitpicking at all. This must tell you that you guys are on the right track.
Re: Show HN: Webflow - Design responsive websites visually
#59Re: Show HN: Webflow - Design responsive websites visually
#60Do you mind telling us about the stack? It's a pretty impressive UI. Feels very native.
Sure! It's Node.js (pretty vanilla Express) on the backend, but most of the heavy lifting is in the browser. After trying Angular, Backbone and Ember, we settled on KnockoutJS for multiple reasons (that's a whole post in itself), the main one being performance (though some may find that statement shocking).