Life before Webflow
Before JT started using Webflow, his web design process meant spending a lot of time in design software, mostly Figma. And because he didn't do much web development himself, the next step meant handing his designs off to engineers through their design-to-developer handoff tool, Zeplin.
Before a developer could bring his designs to life, though, he had to jump through several hoops. That included marking up mockups with specs, using something like Principle to prototype some animations, and giving the developer some sense of his artistic direction. After that, it was a waiting game.
Life after Webflow
Once JT tried Webflow, he was impressed with the complexity and flexibility of the product. In his words, “Webflow is the first web design tool I’ve used that felt like more than just a prototyping tool — and gave me the confidence that I publish what I built with it.”
Building and collaborating on new sites
Now that JT can design and build sites directly in Webflow without needing to spend time coding — or waiting on a developer to ship it — he was able to move a lot faster. And his copywriting partner, Matt, can easily jump into the Editor and tweak copy without breaking the design. With Webflow, they can collaborate seamlessly, then jump into the production phase a lot quicker.
Once the site is built, JT can set up hosting, and invite clients to update the site right within the Editor. In other words, Webflow makes it easy to build, ship, and manage custom sites across different teams.
There's a big chunk of that web design process that I can skip now. I can sort of merge the prototyping and development phase, which has helped me build client sites a lot faster.
Heco is a design studio that makes better user experiences and more interesting brands. They're big on prototyping, collaborating, and trying to find inner peace. The team’s aim is to make things that “earn their spot in people’s lives”.