Tom Johnson
1 min readMay 26, 2017

--

Totally different tools. Apples to Oranges.

Webflow is for designing and building html sites, Figma is for designing anything, but cannot export code beyond selecting an element and copying some css attributes.

Personally, I stopped designing for web-based products and sites in Sketch some time ago. I couldn’t communicate the entire picture clearly, and found that my time was better served just building what I wanted straight in Webflow. For native apps, though, there isn’t anything close to how it works, so I’m forced to do comps, documentation, and hope for the best.

I should say this. As soon as a tool is released that allows me to build my own native (emphasis on native, none of this webview crap) front end design, I will fall head over heels for it. Figma is far from perfect, but it is far better than Sketch. My rock and a hard place is my frustration is being able to almost fully articulate what I want in web, via Webflow, and feeling like I’m beholden to how iOS and Android behave, which at times is very frustrating. Just the other day I spent 30 minutes arguing with a developer on whether to add a shadow to a view controller in iOS programmatically (as I wanted) or by using an exported asset with a shadow applied to it (which horrifies me).

Anyways, I’m not sure it’s fair to compare the 2.

--

--

Tom Johnson
Tom Johnson

Written by Tom Johnson

Design at www.basedash.com. Formerly Principal Designer @Asurion. Personal site -> www.tomjohn.design

Responses (1)