Tom Johnson
1 min readMay 26, 2017

--

I design for native and web apps. Anything for the web, I use Webflow. Keeps the designs constrained, allows me to use their cms for mock data, and I also use it for documentation. I used to mock it up in Sketch and then maybe do some work in Webflow, but I was having to spend way too much time explaining how I wanted things to work instead of actually just making them. I may go into some more details on this in a later post. I don’t do too many web sites, more web-based products that live in a chromium shell. I’ve built a series of angular components that I can reuse to make the UI. Also, I’ve even started using it to make prototypes by creating micro sites instead of relying on Invision or marvel. Those are fine, but they just add more unnecessary work, IMO.

For native, I use a system of default OS components in Figma to build out the screens. I actually do quite a bit of design work in Principle as well, which is a little unusual. I never liked the Principle Sketch integration, because symbols and layer overrides just don’t work, but I really love Principle. I’ve found that layers in Sketch are never organized the same as they would be in Principle, since it relies so much on layer names. For a few projects, I’ve actually done all design work in there and then reverse designed it into Sketch, and now Figma.

--

--

Tom Johnson
Tom Johnson

Written by Tom Johnson

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

Responses (1)