"Any application that can be written in JavaScript, will eventually be written in JavaScript."
[1] http://www.codinghorror.com/blog/2007/07/the-principle-of-le...
3,663 karma · joined October 5, 2008
I'm a co-founder and CEO of Webflow (YC S13). We're cooking up some amazing tools for web designers and developers. If you're interested in joining our team, send me a note to vlad@webflow.com :)
"Any application that can be written in JavaScript, will eventually be written in JavaScript."
[1] http://www.codinghorror.com/blog/2007/07/the-principle-of-le...
- Webflow is meant for production site implementation, so your actual "source" files would be on your computer (in Photoshop, etc). You'd still need to use PS to slice images, optimize them, etc - we're not trying to replace Photoshop wholesale, just improve the workflow around the actual creation of the live site (something for which Photoshop was never intended).
- All your work completed in Webflow (to implement the initial design, and make it responsive), can be easily exported to a full HTML/CSS/JS bundle that can be run hosted anywhere you wish. A good practice could be to download completed sites and archive them in source control as a contingency.
With Webflow, we're looking to build a more comprehensive hosted platform that allows designers to create production websites and actually deploy them live. Down the line, this means that content management, functional web forms, eCommerce integration, and a variety of other things are possible out of the box, without the need to export code and change it manually. Even simple things for programmers like script compression/concatenation and CDN acceleration (all of which happen after the design phase) are hard for many designers to set up, so we want to take as many headaches away as possible so designers can get back to work.
138 days ago, we posted a Show HN [1], and the feedback was so massively encouraging that we doubled down on building the best possible responsive design platform imaginable. Thank you HN for playing such a big part in the first chapter of our young company.
The fact that such a complex workflow (creating static designs, outsourcing coding, manually integrating with a backend, etc) is still being asked of creatives in 2013 boggles my mind.
With a bunch of web-focused tools just now starting to get off the ground - like Easel, Divshot, Jetstrap, Webflow (my company), Froont, Jetstrap, Macaw, etc etc - it's exciting to see Adobe get some real competition in the web space. The demise of Fireworks may actually be a blessing in disguise in the long term.
Right now, there is not one "marketplace" where a business owner can go to find the best designers, especially for websites. Without knowing their options, I've seen many businesses settle for a) a crappy site by their local yellow pages outfit b) the first result for "[my city] web designer" c) one of those do-it-yourself site builders or d) no website at all. A centralized directory of vetted designers makes a lot of sense for easier discovery.
One other thing that would make sense is an Airbnb-style rating system, so designers can start earning a verifiable reputation based on prior work that originated through Scoutzie.
According to Netcraft [1], there were over 600MM active sites [2] last month.
[1] http://news.netcraft.com/archives/2013/04/02/april-2013-web-...
Personally, I feel like I got married at the perfect time in my life (I was done with school, had a great job lined up, etc), and have never regretted that decision. My wife helped me re-focus on the important things, and inspired me to pursue my dream of starting a company.
However, the majority of my Russian friends who were married in their very early 20s have seemingly stagnated in their professional (and even personal) pursuits. Most were married either before or during college, and have either dropped out or are pursuing their education on a very limited part-time basis.
My experience is completely anecdotal, but it seems like getting married early (18-21) has significant drawbacks. Perhaps the sweet spot is somewhere between there and the current late-20s average.
I've been doing freelance web design on the side for a long time (actually bought the webflow.com domain in college for that purpose, going into a lot of debt in the process), then worked at Intuit for several years on an a social enterprise product. Studied CS at CalPoly, and spent a few years wandering through art school in SF before that.
My brother (Sergie) studied at UCSD and worked as a creative director for MuirSkate.com prior to starting work on Webflow. You can see his (now outdated) portfolio here: http://sergie.info/
We're actually big fans of the MailChimp pricing model (both pay-as-you go and monthly options), so it's a possibility.
About Bootstrap, the current demo already uses it for the non-visual elements (grid, etc), but we're still not sure about a whole-scale import yet. There are a lot of changes afoot with Bootstrap and Foundation (mobile-first being a big trend), so we're noodling on a ton of options.