12/24/2023 0 Comments Figma vs zeplin![]() Figma folks were kind enough to host workshops and training sessions, and we scoured the internet, absorbing every YouTube tutorial and Medium article we could find. Unlike other tool migrations we’ve participated in, this one didn’t have any experienced designers to help guide the process. When we started implementing Figma, our first hurdle was our inexperience. Ready to make the leap? We can help you plan a customized transition to Figma-ensuring your product design team stays on track and on schedule. Talk with the experts about your Figma transition We were quickly approved for a pilot run of Figma. And with more and more work moving to remote-first, collaboration was at the top of everyone’s mind. So we sat down with our design neighbors working on other products and product UX leadership and pitched the idea to test this new application.Īs one of the first teams to adopt Abstract when it was introduced, our leadership was open to change and enthusiastic about remaining cutting-edge in the UX environment. It also seemed like our industry as a whole was preparing for change, and we wanted to be at the forefront of that. Our product team heard great things about the tool, and we started entertaining the idea that Figma could potentially transform and integrate our design process. ![]() They had just released several groundbreaking features, like auto layout and component variants. The SolutionĢ020 was a challenging year for nearly everyone, but Figma was making strong advances. But our already siloed design workspaces made it cumbersome to build and govern assets. An enormous corporation with a burgeoning digital footprint is going to need an equally prodigious design system. Our design system was more of a disaster system. We were siloed and isolated in private Abstract projects, forcing the team into disparate processes with different structures, assets, and general working methods. We had multiple products, each with their own team, under the product design umbrella, at a company with many other design departments, each with their own teams. Maintaining a clean and organized design asset repository across multiple apps led to miscommunications and frustration throughout our team.Ĭohesion was a major headache. But there were often latency issues updating those files, creating confusion around the source of truth. When it was time to share UI components with our developers, we used Zeplin. Collaborating and reviewing work in Abstract and Invision never quite fit our workflow. Sketch was a fine UI design tool, but it only runs on macOS, excluding a significant chunk of the potential contributor pool on our client’s team. In retrospect, we were spending huge amounts of time managing this intricate dance. Then we’d deliver our work via Zeplin when it was time to hand it off to developers. We used the Craft plugin to upload our work to Invision for high-fidelity prototyping and review. Sketch was our primary design tool, with Abstract as our collaboration and version control application. Meanwhile, we were using four tools to do a single job. We also didn’t take Figma too seriously because there seemed to be a new design tool released every month, all promising the same thing-a collaborative, cohesive, efficient space for designers to work in-but delivering far less. We were aware of Figma, which had been around for years, but we’d heard about bugs and missing core features. As an early new year’s resolution, we set ambitious reconstruction and clean-up plans that stretched over our upcoming slow holiday period. During that time, our design system files devolved into a mess. Our team was consulting for a Fortune 100 company, and we had just wrapped up another year with our usual design applications, Abstract and Sketch. It was a problem shared by most UI and product designers in the world at the time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |