Zeplin, from the company of the same name, is a platform supporting collaboration in application development by engineers and designers by providing an API with popular collaboration, development and prototyping tools and creating a space where productions can be shared and reviewed.
$0
per user per month
zeroheight
Score 8.6 out of 10
N/A
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be easily shared across teams.
I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design …
I still have some issues, especially with color integration between the style guide and also project. When we update the colors, it's not automatically sync to every project. Aside from that, zeplin solves my problem for hand-off design from design to developer. I set zeplin is source of truth design file
For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.
Ease in automatically building design style guides, saving time that might be spent on building style guides in another tool (such as InDesign).
Users can use Mac, PC, or web versions of this app to collaborate on a single project, enabling us to work with a wider pool of contractors.
Accelerates the design-to-development workflow, as it’s very easy to import Sketch or Photoshop files through plug-ins, and HTML/CSS codes are automatically created based on designs.
Provides cross-platform specifications for web, iOS, and Android, which can save developers time in figuring out specifications beyond the “main platform" on their own.
when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that
-Inconvenient table of contents; -Search only checks screens' names in the Zeplin project, not checks text on the screens, even though it's stored there as text and can be easily read from a technical perspective; -I have to log in too often. This is too secure for such an application
Zeplin has classic support with a chat from the website. It's working fine, and we're also getting the support needed when needed. However, Zeplin is very good at closing the incidents and moving on. It was a while ago we had a case with their support so that it might have improved since then.
Zeplin is great to inspect and share user interfaces, specifications and assets, perfect for developers. Tools like InVision and Marvel are much better to create prototypes for both developers, coworkers and even stakeholders, but they don't have this kind of feature (inspection) as Zeplin does. So each of them can be used for different purposes, offering different approaches to share and interact with layouts for apps and websites.
I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.
Development time has reduced as the design updates are communicated in real time to developers and they don't have to write the boilerplate code as it's already generated.
Employee engagement has improved as every stakeholder is aware about the design changes from the beginning and can give their inputs.
Designers save a lot of time as they don't to explicitly communicate when the update or publish their designs and also it just takes a couple of clicks to publish their designs. Also, lot of rework is saved as every stakeholder is involved right from the beginning.
increased quality, as less misunderstandings or communication problems occur
increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.
