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.
Marvel is a pretty expensive application for what it gives you, it is a pretty good tool but I think the handoff is not as good as Zeplin's. I think the style of Zeplin is more oriented to developers and Marvel is more oriented to the designers. I like the way Zeplin is …
Marvel is a very strong tool in scenarios where designers seek to quickly create simple prototypes on their desktops using a simple, intuitive interface. It offers “just enough” functionality to create somewhat realistic designs to present to stakeholders and other designers. However, there’s a limit to how “realistic” those designs can be, given that Marvel has somewhat limited functionality around animations. Marvel is not a strong option for those who want to create very complex prototypes with many animations, or for those who want to edit prototypes on their tablet or phone. Marvel is a jewel for simplicity but starts to be difficult to use when creating complicated designs. For creating more complicated prototypes, I would recommend a more robust tool, such as Axure.
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
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.
I really miss being able to duplicate, make a copy of the prototype I'm working on. Sometimes, I want to make a comparison with detail changes and without being able to duplicate it is difficult.
Compared to other similar services, I feel the animations could be more fluid and smoother.
It could have more free sophisticated icons and images.
Zeplin's component management and style guide help us to be consistent across whole product and it so easy to use for non-technical person. It is now easy to collaboration for designes between different teams like stackholders, product owner, UI/UX, developers and testers. Now there is only one point of reference is Zeplin so it is so easy to get details without asking designer or developer again and again.
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.
Ultimately, InVision was just a better fit for our company's needs. It's probably faster to create prototypes using Marvel, but InVision's collaboration features (comments, notes, etc.) are much more robust, which was helpful for our large team spread across multiple continents. InVision also offers more advanced features, and Marvel felt a little too limited for our overall business needs.
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.
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.
