![]() File synchronization didn’t work well between different machines.In an ever-growing team, you occasionally wonder how processes can be made better: search and transfer of design files, tools that work correctly, and a good understandable component library.Īt one of the team retros (there were 11 of us then, and the number of Semrush products increased to 44), we decided to discuss tools and work with files, library, and development teams.Īt that time, the team jokingly defined emotions for ourselves in relation to the tools we were working with: We had folks who were passionately campaigning to move to Figma, so the fourth column in the picture shows the confrontation situation regarding these tools on the team.Īfter this warm-up, we’ve already collected several problems that have become defining for us in the transition to the new tool. On that note, everyone was supposed to be happy and cheerful. To do this, we held small meetings, where we gave each other tips for working with Sketch.Īt the same time, we started a channel in corporate Slack to share plugins, tips, and problems. ![]() It took a month or two for the team to get used to working in the new tool. And we continued to store the files in Google Drive. Our set of working tools changed to: Sketch → Zeplin. In the end, some of them came out like this: And a lot of nesting in the symbols was unavoidable. Some of our components had a lot of variations, so the library was very large. One of the designers started building a library of symbols in Sketch, kicking around and playing with crutches. It was a dubious but hopeful tool back then. Especially after moving pixels around in Photoshop and constantly running to colleagues and guides in pdf and png to remember what the indents in the buttons were.įigma had no functionality with components at that time. The prospect of building a library of symbols in Sketch that could be reused in different files seemed magical to us. Just then, Bohemian Coding added functionality for creating cross-file symbols. How it was before we switched to FigmaĪt one point, we were lucky enough to move from the needle of Photoshop to Sketch. We hope that our experience and the questions we asked ourselves when moving a large design library between tools will help other teams do it just as painlessly and quickly as we did. That said, of course, we're very grateful to Sketch-it taught us how to work with libraries and UI components, and to constantly learn new things. In this piece, we’ve collected the pains our design team went through while working with the tools we used before we switched to Figma. And all the layouts were stored on Google Drive in carefully or not-so-carefully grouped folders.ĭoes it hurt? If you’re a designer on the product team, the old Harold’s face smiling through the pain meme should come to your mind right now. It was small (five people), there were few products in Semrush (11), and the source of truth for styles and indents was a library with buttons and some basic inputs in smart objects in Photoshop.īack then, the toolkit looked like this: Photoshop → Zeplin. Once upon a time, our UI team was young and carefree. We describe the pros and cons of all of them and share our checklist for a painless change of tools. How the UI/UX design team switched to Figma and why we weren’t satisfied with Zeplin, Sketch, and Google Drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |