This keeps developers informed about updates. You can clearly communicate and label design iterations each time you push a new design to Zeplin. Labeled components also link to the broader style guide for easier development. For example, seeing a button when pressed or hovered. Clicking the label lets developers see component properties, or they can see the same component in different states. You can label elements that are linked to something in your component library. On the developer’s end, they can filter based on tags to work on specified design elements or hide irrelevant pages. Then you can assign other elements to existing tags to manage multiple design aspects at the same time. If a design element needs changes, you can mark it so dev teams ignore it. There are too many to list here, but these are some of our favorites:ĭesigners can tag areas and pages to communicate with developers. Teams get access to a huge range of helpful features. That’s what we’ll compare in this section. However, Figma does offer handoff tools that are similar to Zeplin. One is for design, the other is for handoff. The system is developer-friendly, and it reduces miscommunication by effectively bridging the dev-design gap.įigma and Zeplin are made for very different parts of the UI development process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |