But with the rise of cloud-based services like Google Docs, the delivery workflow of Sketch felt somewhat archaic. That is, single large files stored locally, requiring a licensed copy of Sketch on any computer that needed to view the file. While Sketch improved the web design tooling, it still followed similar delivery mechanisms of the old days. Sketch, with its interface-focused vector tooling and comparatively cheap price, answered many of the shortfalls of Photoshop for web design and became the tool for designing websites on Mac. In the past five years, there's been a large uptake in Sketch for web design. While there were a few others tools better suited to interfaces, like Adobe Illustrator and (Macromedia/Adobe) Fireworks, many designers still chose Photoshop. Also, the filters and effects that Photoshop provided did not always translate well to CSS. Multi-page designs meant multiple Photoshop files, and shared colours and components just werenвЂ™t possible.

However, Photoshop was not built for creating web interfaces, and as the web moved to responsive designs and high resolution displays, being raster-based meant additional work was needed for adding and exporting vector icons at different sizes and different file types. Perhaps this is why Photoshop, a photo-manipulation program, was the ill-fitted tool of choice for designing web interfaces for many years. Regardless of promised benefits, the idea of learning a new tool can often frighten rather than excite. Many people, designers included, don't like change. It looked like a simple vector web-app at first glance, but the more we saw, the more we realised this had potential to change our whole design/delivery process in ways similar to how Google Docs revolutionised sharing word documents. However, when one of our developers was looking for a Sketch alternative to perform frontend development on his Linux laptop, we stumbled upon Figma. Salsa Digital, like many digital agencies, has been designing in Sketch for years.

Figma vs sketch