Sympli vs Zeplin: What are the differences?
Developers describe Sympli as "Design version control, handoff and workflow tool". It delivers all design components and assets to your team members where they work enabling quick commenting, implementation, and testing. It supports your team by connecting each team member with the collaboration and automation tools they need to work more efficiently. On the other hand, Zeplin is detailed as "Collaboration app for UI designers and frontend developers". Collaboration app for designers & developers. Supports Sketch and Photoshop (on beta!).
Sympli and Zeplin belong to "Graphic Design" category of the tech stack.
What is Sympli?
What is Zeplin?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Sympli?
What are the cons of using Sympli?
What are the cons of using Zeplin?
Sign up to get full access to all the companiesMake informed product decisions
The tool we use for editing UI is React Storybook. It is the perfect place to make sure your work aligns with designs to the pixel across breakpoints. You get fast hot module reloading and a couple checkboxes to enable/disable browser features like Flexbox.
The only tricks I apply to Storybook are loading the stories with the mock data we’ve extracted from the API. If your mock data really covers all the various various possible states for your UI, you are good to go. Beyond that, if you have alternative states you want to account for, perhaps loading or error states, you can add them in manually.
This is the crux of the matter for Storybook. This file is entirely generated from Yeoman (discussed below), and it delivers the examples from the Alps Journey by default. getSectionsFromJourney() just filters the sections.
One other hack you’ll notice is that I added a pair of divs to bookend my component vertically, since Storybook renders with whitespace around the component. That is fine for buttons or UI with borders, but it’s hard to tell precisely where your component starts and ends, so I hacked them in there.
Since we are talking about how all these fabulous tools work so well together to help you be productive, can I just say what a delight it is to work on UI with Zeplin or Figma side by side with Storybook. Digging into UI in this abstract way takes all the chaos of this madcap world away one breakpoint at a time, and in that quiet realm, you are good down to the pixel every time.
To supply Storybook and our unit tests with realistic mock data, we want to extract the mock data directly from our Shared Development Environment. As with codegen, even a small change in a query fragment should also trigger many small changes in mock data. And here, similarly, the hard part is tackled entirely by Apollo CLI, and you can stitch it together with your own code in no time.
Coming back to Zeplin and Figma briefly, they're both built to allow engineers to extract content directly to facilitate product development.
Extracting the copy for an entire paragraph is as simple as selecting the content in Zeplin and clicking the “copy” icon in the Content section of the sidebar. In the case of Zeplin, images can be extracted by selecting and clicking the “download” icon in the Assets section of the sidebar.ReactDesignStack #StorybookStack #StorybookDesignStack
We use zeplin as an interface between designers, developers and stakeholders for sharing, improving and discussing designs