I dove into Webflow for the first time over the weekend.
Why?
Because I’m considering moving a client project from Squarespace to Webflow.
Squarespace was a wonderful option to get an MVP out into the world without hiring a developer.
But now that the product market fit has been proven, the design limitations are a sore spot.
So what do I think about Webflow?
In a nutshell, I’m impressed. I’ve built out websites using Squarespace, WordPress, and coded them from scratch.
And I can tell you, I’m very excited about Webflow, and here’s why:
1. You get the power of HTML and CSS as if you coded a UI from scratch
2. You get some of the ease of a drag-and-drop platform
Now, there’s a learning curve here because the Webflow designer is built on foundational concepts from HTML and CSS (think the HTML Box Model, Flexbox, and CSS Grid). It’ll help you significantly to understand these. In fact, you might be able to do little if you don’t understand them. But, if you don’t know them, not to worry, Webflow has some awesome, succinct, high-quality tutorials).
3. You don’t need to hire a software developer or have a front-end dev on staff to maintain your website, e-commerce store, or CMS
So
If your goal is to get a website live as quickly as possible, you don’t know HTML or CSS, you don’t have the time or desire to learn them, and you’re not interested in hiring a developer - go with a classic drag-and-drop platform (think Squarespace). Quick and Easy is what these are awesome for!
However, if you have a couple of weeks to devote to learning HTML and CSS, I’d choose Webflow, it’ll give you light years more control over your UI.
Webflow can eliminate over-engineering for those of you who don’t need custom software and give you the power to create a fully customized UI with the precision of HTML and CSS.
Katherine is a Software Engineer, and an Anthropologist at heart. Always curious about the why and how. She’s a creator, keen observer and pattern matcher. At the beginning of her career, she developed processes to solve and prevent recurring problems. One time, the solution required her to work with a software developer. A seed was planted. The next time code was required, she learned HTML and CSS. Soon after, she decided to become a developer. Forever curious, and equal parts researcher and executor. Katherine has worked in the medical device, outdoor and software consulting industries.
Contact us to schedule a free 30-minute consultation to discuss your current pain points and challenges.