Frederic Ewen English professor at Brooklyn College from 1930 to 1952. During the height of the McCarthy period Ewen was forced to resign his teaching position.
Thoughts on design software and why we migrated the Unsplash Design Library to Figma.There was a time when life was simple: I was a college student with an “extended trial” version of Photoshop and Illustrator—all you needed to get started in web/graphic design. Throw in Notepad++ if you dabbled in code.
How things have changed. Until recently, we’ve juggled multiple subscriptions to handle our team’s product design and development stack: Creative Cloud, Sketch, Abstract, Marvel (at some point we also had InVision and Redpen), Dropbox, Trello, GitHub and Slack just to name a few. All amazing companies/services that make our work life, to an extent, a little easier.
As a result, having an abundance of services lead us to an overcomplicated design workflow: jumping from Trello to Dropbox Paper to Sketch files scattered throughout Dropbox.
Before we dive into why we switched to Figma, let’s take a step back and look at why we switched to Sketch in the first place.
Charles Deluvio and I were those guys: solely designing in Adobe Illustrator—while the majority of designers were using Adobe Photoshop for web and interface design. When Sketch picked up hype, most of the shiny features that wow’ed Photoshop kids have been a long time part of Illustrator: art boards, vector-based, SVG support, grids, small file size, symbols, etc. We gave Sketch a shot but never had a good enough reason to jump ship to an unstable software that might not even exist tomorrow.
Fast-forward to a year later and most designers have shifted to Sketch, while we were still rocking Illustrator. Then came along Sketch 3—with introduction of symbols, major improvements to speed, templating, SVG support, better style handling and more. We had also happened to hire a new teammate who was a Sketch user. This made us re-visit Sketch, fall in love with its speed, simple UI and focus on interface design—ultimately pushing us to work in Sketch and transitioning over.
Sketch set the new standard for interface design tools. Sketch is king 👑
Sketch was king. Today, we have choices. Competitive choices between some industry heavy-lifters: Adobe XD, Figma, Framer, InVision Studio, Sketch, UXPin—and probably more that I’m not even aware of. Each company is trying to sway us into using their product by providing solutions to some of our “problems” or by simply offering a better alternative. These solutions are driven by marketing, fancy presentations and hype. Mainly hype.
After trying out numerous αlphas and βetas, the line between apps quickly blurred: sleek UIs, libraries, component-based, responsive layout support, prototyping baked in, etc. Each tool is piggybacking on each other’s weaknesses.So how do you choose?
For a long time we didn’t. We’ve put these αlphas aside and went back to using whichever tool we were most comfortable with and was getting the job done—for us it was Sketch.
Fundamentally, file naming conventions, file management and versioning at scale became cumbersome over time. We had a system in place to handle it all, yet it kept failing. As a result, we’ve ended up with numerous Sketch files scattered throughout our Dropbox.
There are even numerous tools and plugins to help you organize and keep your Sketch files clean. Welcome to Plugin Hell 🔥
As a first solution, we decided to go over our file naming and handling process—but since Figma’s name kept popping up in our conversations, we could no longer disregard it. The more we looked into it, the more it made sense.The idea behind Figma was a breath of fresh air from the rest of the herd.
I won’t go into details about how we migrated to Figma, but rather outline the steps that we took that helped us switch confidently:
© 2023 Navana - Navana. All copyright reserved by Electronthemes & Published with Ghost.