Quando você entrou sem código e o que o levou a querer iniciar sua empresa?

Oficialmente em 2004, quando eu estava trabalhando em uma agência e tive a idéia original do Webflow - tratava-se de remover a necessidade de um codificador no meio de um designer e do cliente.

Eu estava trabalhando com uma agência que tinha clientes muito grandes como Apple, HP, Quicksilver, etc. E um dia, vi a fatura de um desses clientes, e era tão astronômica! E pensei, ok, há uma oportunidade aqui onde podemos remover a barreira entre o que os designers querem e o que realmente acaba entrando no ar no site.

You know, for the longest time, when we started Zapier, no code wasn't a thing. Right? No code has really been a thing that as a “term” has existed since, what, 2018? 2017? Maybe it's fairly new and so we, you know, we started Zapier in 2011. And at the time, we sought out to solve what felt like a somewhat simple, but fairly pervasive problem, which is that there's all these new apps that are popping up left and right, and all the customers, all the end users of these tools, want them to work with everything else that they use.

Now almost a decade later and our job at the time was like, well, maybe if we just made it a little easier for the end user to be able to set up an integration between those tools that could be useful. And turned out over time, it's more than just useful because all these end providers, you know, the MailChimp, the Salesforce, the G Suite's of the world, it's really difficult for them to build a big ecosystem of integrations, it's just a hard thing to do. Even if you are a very successful business.

We realized that over time, Zapier had a much bigger value to play. It wasn't just helping with these like little simple one-off integrations, but it really acted as a bit of a workflow tool that helped folks connect these tools, but in a way that actually felt more like building workflows. It felt more like logic. It felt more like coding, in some sense. In some ways, even though most of the people who use Zapier don't know how to code, many of them don't know what APIs even are and so just the ability to help people connect the building blocks of the web together in a way that creates a thing has been something that I think when no code became a term and a thing, it was like, well, Zapier is the thing that provides all the logic for all these tools.

I started building without code in probably 2014. I had an idea for an app that was going to help people find an affordable art for their homes. And this was really before a lot of the no-code tools today. So my first experience building code was taking tools that were not intended to be app builders and kind of hacking them to create an app-like experience.

So for the app whenever someone signed up, they told us about what kind of art they liked, for example photography or like paintings. And then we would ask about their taste. But we would use the survey software to show and hide different things based on their previous answer. So that was my first no code experience — taking a survey and hacking it to kind of create an app-like experience for my customers, and using it dynamically show them art recommendations. People would actually email me back and say, ‘Oh, my gosh, your app is so cool!'  We made our first $35,000 with that hacked together survey.

I think about six or seven years ago, just before I joined Product Hunt, I was trying to build stuff and trying to look for ways to build that without having to learn to code. And I was doing it a little bit with no-code tools. What I didn't realize was the thing that people were actually interested in wasn't the actual ideas I had, because they all sucked. It was actually the ability to build it really quickly, and make it feel like software. And it was all built without code. Everyone was asking how did you build these things without code? So I thought, okay, I'll just show you how to do it.

Acredito que sempre estive fazendo a coisa sem código. Quando comecei a trabalhar como engenheiro, uma das minhas tarefas era criar software e produtos que não exigissem que os operadores de negócios precisassem me contatar o dia todo para fazer alterações. Portanto, acredito que, como engenheiro, o no-code sempre me chamou a atenção do ponto de vista da arquitetura e da perspectiva do design e do produto. Dessa forma, a tecnologia pode ser mais um facilitador. Portanto, acredito que, fundamentalmente, tenho isso desde que comecei no comércio eletrônico como engenheiro, em 2009.

I got into no-code before no-code was nearly as popular as it is today. But that was back in 2017 and I really saw the rise of design tools with Figma, Sketch, and Invision — all those tools becoming really popular. But there wasn't really anything that took what you built and translated into a real product. So what I wanted to do is basically take that and build a product that let you build a fully functional mobile app, but not having to know how to code.

I've been doing some version of no-code for a while. I've worked in a lot of different industries, and in each we had some version of embracing no-code or low-code tools. And when you look back at when I was first getting into technology, I would building websites with Dreamweaver or Visual Basic.

We started building Draftbit after trying to build a different business — a mobile app. We were sort of just frustrated, even with great co-founders, at hard it was to get the first version of our mobile app out the door. We realized that we really were passionate about making it easier for us, or anyone, to get our first version out and iterate on it.

I think I got into no-code before I really knew what no-code was just by playing around with no-code tools maybe like five or six years ago. My intro was Zapier, the holy grail of integrations. I've always been at this intersection of technical and non-technical and I've always found no-code as a beautiful mix of those things. 

No-code is really, really part of the tech stack that I use on a day to day basis and teach amongst even my own team, so I thought why not join a company like Voiceflow, who's gonna make a really big impact in the voice space and the no-code space?

In terms of getting started with no code, when it comes to design, back in the day Dreamweaver was my earliest experience with no-code.

I guess my excitement in the no-code space was sort of reinvigorated just more recently, obviously, as 8020, came to life. I got an opportunity to officially join and kind of steer the ship. Obviously getting back to scratching that itch from a design perspective has been great, but then also just kind of more broadly to start to help, along with everybody else, figure out a lot of what this means, is kind of the exciting part.

[Tenho experiência em criar com código e comecei apenas fazendo meus próprios sites, HTML, CSS, e depois realmente entrei no WordPress e desenvolvendo temas personalizados para WordPress. E então comecei a trabalhar em um projeto onde eu tinha recursos limitados e estava tentando construir muitos sites e é como: "Tem que haver uma maneira melhor de fazer isso. Isto é tão, tão difícil" E então encontrei o Webflow, e fiquei tipo, "Oh querido, vamos tentar!"

[Matt] Em termos de Visual Dev FM, foi originalmente formado em torno da idéia de que Ben e eu tomamos café todas as sextas-feiras só para falar sem código, e nerd para fora, e começou de nós sermos como, deveríamos - o pensamento mais básico de todos os tempos - deveríamos começar um podcast sobre isto. E assim fizemos, e então conhecemos Lacey e o podcast ficou muito melhor.