Sketch vs. Figma – pick a side
Jun 08, 2020
Let's join forces to create something great 🤝
Jun 08, 2020
Our design team recently made the decision to switch from using Photoshop CS to Sketch, certainly where UI design was concerned.
Admittedly, we made the switch quite late, but after having a number sessions playing around with Sketch and experiencing the lightness and speed of the app, we were very much sold.
Well, until very recently.
Not to say that we jump around with every new design tool that becomes available, but there was one feature in-particular that caught our very active creative eye and warranted further investigation from the team.
For us, the following is insight behind our decision making to make a transition from Sketch to Figma.
Our design team is BIG on taking a collaborative approach on all projects we undertake. Whilst Sketch allowed us to share files via the cloud for other members to download and re-upload, Figma provides a real-time experience where you could literally be designing with a colleague whilst speaking to them on a video call or on Skype.
A very strong selling point for us. Of course, it would require a degree of access management as you don’t want your design process to have the chaos that the intrusion of a myriad of voices can bring.
The ability to create components is a must. Components – as you’d expect from a development perspective – allows you to create instances (duplicates) of a single set of grouped elements. You can modify attributes of these instances, but the main skeleton remains in place.
The Auto-layout feature provides the capability of creating components that automatically snaps the elements contained within it. You you could drag an item above an element to the space below and it would shift into the ‘best-fit’ position.
You can read more detail about Auto-layout on uxdesign.cc where they go into much more of the minute details to help paint a better picture.