I absolutely don't think this is the case, and paradoxically something like Webflow actually creates more demand for coders and software engineers. Today, only 0.25% of the world knows how to write code, meaning the amount of software being created is limited to that subset of the population. No-code tools potentially will raise that percentage to 25% or even higher, meaning 2 orders of magnitude more people are potentially starting new software projects – however small initially.
Inevitably, those projects will need more functionality than visual or declarative abstractions currently allow, which raises demand for code-based developers. Code will always outpace higher-order tools in flexibility and power, and coders will always be in demand.
Think of it like what happened with spreadsheets... initially there was a lot of fear that moving e.g. financial modeling workflows from e.g. Pascal, etc to visual spreadsheets might make developers less relevant. But that's the opposite of what happened.
Sure, there might be some developers who only do very basic tasks like converting a PSD file to HTML/CSS, but that started fading out as a highly sought out skill even before Webflow was prevalent. But there will always be a need for devs, and there's a massive shortage of them in the world still, so I'm honestly a lot less worried about this.
Now came the time to get users. We were targeting mostly designers and non-technical folks – so we posted it on Digg (heh, remember those days?), Reddit, and several designer-centric forums. But none of those posts got any meaningful traction. We were at a loss.
Then, with tempered expectations about how a visual development tool for designers would be received in the hacker community, we posted here to HN. The title was “Show HN: Webflow – design responsive websites visually” [1] and we crossed our fingers really hard at this last-ditch effort.
What happened next was nothing short of life-changing. The post took off like wildfire, staying at #1 for the entire day. Incredible words of encouragement were all over the comments. Over 25,000 people signed up for our beta list. VentureBeat wrote a story about us that same day. Tons of people started talking about Webflow on Twitter, Reddit, etc as a result. This led to a ton of word of mouth and even more signups.
This amazing traction helped us get into YC several months later, gave us momentum to raise some funding from some angel investors, and most importantly gave us the confidence that we were truly on to something that can be really valuable for the world.
Since then, Webflow has grown to millions of users, over a hundred thousand customers, and over 200 team members. I still have to pinch myself when I see that Webflow has somehow become one of the top YC companies of all time. Out of our customers, tens of thousands use Webflow exclusively to make a living – to run an agency, build websites and light applications, create websites for clients, or for their own startups. Tons of YC startups (e.g. lattice.com, hellosign.com, many many more) now use Webflow to run their marketing.
I’m 1000% convinced that if that HN post did not take off, we would have gone back to our jobs and that early Webflow demo would have been a mere mention on our resumes somewhere. Thousands of people wouldn’t be empowered to build for the web the way they can now. I can’t imagine what that alternate future would be like, and it hinged seemingly on just one submission to this community.
So this is a very belated, but very huge THANK YOU to HN for being kind to a trio of co-founders who wanted to make something valuable for the world, and were at the end of their rope in many ways. You gave us confidence, hope, encouragement, and a lifeline that got us through the lows of building a startup.
I honestly don't think it was a mistake the first time. We had almost nothing to show for what we wanted to build, it must have looked like a toy at the time. Our first application was more of a "fancier web inspector plugin" with no validation that there was a market for such a thing – I probably would have made the same exact call if I was sitting on the admissions/evaluation side.
One thing to note is that we're also creating visual abstractions over common things that are hand-coded with JS. For example, see our declarative GUI for interactions and animations [1] – it allows designers to get the same exact effects that you'd build out manually, but without the need to learn how to write that JS from scratch.
That is, in fact, our main differentiator – and the main reason people choose Webflow. Check out this very diverse set of sites [1] that can be built with Webflow, this ability to visually develop any kind of custom layout/experience really does go a long way to distance us from any competitors.
Hey HN! I'm Vlad, CEO and one of the co-founders of Webflow.
It was over 6 years ago now, a just several months a rejection email from YC and a few weeks from being essentially bankrupt (my daughter had an unexpected surgery while we had only catastrophic health insurance), we posted a Show HN about Webflow (https://news.ycombinator.com/item?id=5407499). It was our last "hail mary" to show something tangible to the world before promising our partners to go back to our old jobs to actually get some income again.
Luckily, the Show HN took off like wildfire and we stuck to the #1 spot nearly all day. Tens of thousands of people signed up for our beta. This really helped us reapply to YC with tons more traction (and boundless confidence this time), and we were lucky enough to get in to the next batch.
We're now a team of over 120 people across 20 countries, serving billions of requests for tens of thousands of paying customers. I'm very confident that we wouldn't have been able to achieve this had the HN post not taken off here, and we're so thankful for the positive reception. Luckily, we didn't get those funny "I can build this in a day with some bash scripts!" kinds of comments :)
Even though it's been many years since then, we're still on the same mission to empower millions more people to build powerful websites (and increasingly, more powerful software!) without code. We believe that in the end, democratizing software creation will multiply the potential of the internet, likely by at least an order of magnitude.
A HUGE and humble thank you to the community here, and for your support way back when!
A quick clarification - the output of Webflow actually works across all modern browsers, but the design tool itself has more limited browser support.
One of the biggest challenges with Firefox has been the inability to style native scrollbars to become dark with CSS – theres a decade+ long issue/conversation around making that happen: https://bugzilla.mozilla.org/show_bug.cgi?id=77790. Eventually, we gave up waiting on native support, and now working towards converting scrollbars to be JavaScript-driven to support Firefox (otherwise the white scrollbars stick out like a sore thumb in a dark UI).
Almost 6 years ago to the day, I received an email from YC about our application being rejected – I still remember that feeling of almost wanting to give up, but also weirdly motivated to keep going and try again. Despite the setback, my brother Sergie and close friend Bryant and I kept working on creating a prototype that people could actually play with – and a few months later we posted our first Show HN about Webflow (https://news.ycombinator.com/item?id=5407499).
What we showed was very limited and barely worked (you can still see it by following the link above), but thankfully the post took off and over 25,000 people signed up to see our beta in just a few days. We were in awe of the power of HN, and I can honestly say our company wouldn't be here today had it not been for the warm reception and encouragement of this community in that original Show HN post.
Today, we're releasing a brand new CSS playground similar to our first one, this time showing off the amazing power of CSS Grid, which brings a whole new level of power and creativity to the web – especially to those people who struggle with learning to code. It's one small step on our bigger vision to democratize software creation beyond the 0.25% of the world that knows how to code - by offering a visual abstraction over things like CSS Grid, we can actually get more people to understand the principles behind CSS, box model, responsive layout, inheritance, etc. We've also found that tools like this are super useful to backend-focused engineers that don't have much experience in frontend work, at least as a way to ease into frontend.
We'd love to hear any and all feedback! Support for grid autoflow as well as grid template areas is coming in the next few months, but currently manual placement, FR units, and minmax are all supported.
The CSS Grid playground currently works in desktop Chrome/Safari/Brave/Vivaldi, but we're still working on Firefox and tablet support – our apologies if you're seeing an unsupported browser message :\
What we posted got shared in various other places (Designer News, Twitter, Reddit, etc), which might we why it was higher. But Hacker News was definitely the catalyst of it all.
Yeah, the first year even after YC funding was very tough. Long story short: sold a car, borrowed a ton on those credit card write-yourself-a-check 2% balance transfer deals (thankfully had good credit to be able to do that), and withdrew early from an IRA (those penalties hurt!) - wouldn’t recommend :)
Nearly 5 years ago, a few months after being rejected from YC and a few weeks from being essentially bankrupt (my daughter had an unexpected surgery while we had only catastrophic health insurance), my brother and I posted a Show HN about Webflow (https://news.ycombinator.com/item?id=5407499). It was our last-ditch attempt to show a proof-of-concept to the world before going back to our old bosses to ask for our jobs back.
Thankfully, the post took off - we were #1 for most of the day, and over 25,000 people signed up for our beta list in the several days after that post. This helped us reapply to YC with a lot more confidence and traction, and we were able to get into the next batch.
Webflow (https://webflow.com/) has since grown into a profitable business with close to 1,000,000 users all over the world, billions of website requests served, and close to 60 team members in over 14 countries. I'm pretty sure none (or very little) of this would be possible without HN and the community here, and the super positive reception our post had.
Today, we're on a mission to enable more people to create powerful software without having to learn how to code - we probably have decades to make that vision a reality, but we're on a decent start in large part thanks to our launch on HN.
Inevitably, those projects will need more functionality than visual or declarative abstractions currently allow, which raises demand for code-based developers. Code will always outpace higher-order tools in flexibility and power, and coders will always be in demand.
Think of it like what happened with spreadsheets... initially there was a lot of fear that moving e.g. financial modeling workflows from e.g. Pascal, etc to visual spreadsheets might make developers less relevant. But that's the opposite of what happened.
Sure, there might be some developers who only do very basic tasks like converting a PSD file to HTML/CSS, but that started fading out as a highly sought out skill even before Webflow was prevalent. But there will always be a need for devs, and there's a massive shortage of them in the world still, so I'm honestly a lot less worried about this.