![]() ![]() What a pity :(Ĭomments on InVision are on a separate page as the Inspector On InVision they are on a separate page, and the users need to switch between modes. What makes it best on Zeplin is that comments are visible by default on the inspector's page. Is it scrollable? Vertically centered? Is the size proportional? These pieces of information should be left by the designers for the developer to use on integration.Ĭomments on Zeplin are visible when the developer inspects elements Commenting on the mockup to clarify the integrationĬomments are an essential feature to hand over extra information not visible on the mockup or the inspector. Consequently, there are no links between the style guide and the mockups, so it is less maintainable (or takes too much time to maintain) and is less visible for the team. On InVision, if you want a style guide you will need to create one from scratch in Sketch. Reciprocally, the developer can also see on each mockup which components are used and can click the link to see different component states.Ī link to the component style guide from a mockup on Zeplinĭesigners can also share their style guide publicly to get visibility and reactions. You can see how the navigation looks like with 2 and 3 tabs.Ĭomponents and mockup are linked: on the style guide, the developer can see which mockups use which components. These components are reused by the designer on several mockups. The platform detects font properties and colors so the designers can add them to the style guide easily.ĭesigners can add colors to the style guide in one click from the mockup and define a name for eachĭesigners can also export individual Sketch Symbols, which will then appear in the style guide Components section. Zeplin integrates an interface to create a style guide from imported mockups. Style guides on Zeplin vs Invision: why Zeplin wins
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |