Zeplin Reviews and Ratings

Use Cases and Deployment Scope

We use Zeplin to upload our final designs to be attached to jira tickets for dev handoff. I think it also accidentally gets used to organize release designs and be able to go back and find design iterations. The product managers will also use it to show and discuss designs for their tickets, as well as development using it to discuss when issues come up. Our UX architects will upload flows in the projects to be referenced as well. It also was used to hold our design system library for reference for a littler while.

Likelihood to Recommend

I think it just makes it easier to share designs and give a lot of context to developers or others. I personally like uploading to an external program to have people see mocks vs working in the design program. I think it helps cleanliness and organization of projects.

I really like the ease of use and the use cases that many different teams get from using it- from design, to development, to product managers, etc.

Use Cases and Deployment Scope

We use Zeplin as design tool for new UI of the web. As I tester I refers to design in Zeplin to verify with our webpage. By using this tool, Product owner, Designer, developer, tester are working aligned with product specification and requirements. Before this tool, everyone was not able to work in align.

Likelihood to Recommend

The most useful about Zeplin is that we can centrilize design and communicate over that design by adding comments. Which helps to stay on same page for every coress team like product owner, designer, developers and tester. But, Zeplin is not helpful in one thing is that when we have any animation on elements then it is not showing. Overall, I am happy with Zeplin.

Use Cases and Deployment Scope

We used it as a main source of truth for design requirements for our clients, BAs, QAs, and developers. Important needs are to: -share assets for new UI items; -share precise sizes of lines, gaps, etc. for the purpose of accurate UI development; -asynchronous communication between different stakeholders regarding design.

Likelihood to Recommend

It's good for:

-Asynchronous communication using comments related to particular UI item;

-Design storage with the purpose of having a single source of truth, let's call this specification;

-Sharing sizes, colors, assets etc. whatever developers need to develop accurate UI according to this design.

It's not the best choice for:

-To discuss UI in live meetings while making changes on the fly.

Use Cases and Deployment Scope

I use Zeplin as the source of truth in the final design that I hand off to the developer team. Before utilizing Zeplin, my team used to face issues while handing over the design to the tech team. The main issue was that the tech team could not determine if the design was final or not. Even though we had marked the design as final, there were instances where our PM required some changes in the middle of development. This caused a delay in the delivery and made the dev team upset as it affected their timeline and deliverable.

Likelihood to Recommend

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

Use Cases and Deployment Scope

Zeplin is primarily used as a collaboration tool for our UI designers, front-end developers, product managers, copywriters and every other stakeholder in the design and development of the product. It makes the design handoff process efficient by allowing the designer to upload their design directly from the the sketching tools and then basic code snippets are auto generated for the developer as a boilerplate code to work on.

Likelihood to Recommend

Zeplin is more suited for teams that are looking for handoff tool that also has a built-in style guide. It is effective for both large and small project and primarily delivers most benefits when there are a large number of stakeholders. However, if someone needs a design handoff tool along with prototyping, Zeplin is not the right choice as it doesn't have prototyping capabilities.

Use Cases and Deployment Scope

Zeplin is used by several departments across our organization - our product, design, and engineering teams all make use of the software. It allows the product and design teams to do their work and then have a clean handoff to engineering to build out the feature with everything that they need.

Likelihood to Recommend

Zeplin is well suited for collaborating on product design and allowing the designer to include all the necessary notes and details required by the engineer in order to move forward and build what has been designed. It would be ideal to allow for clickable elements with the design to be able to show/experience some natural navigation and therefore be better suited for prototyping and understanding behaviors/interactions of elements.

Use Cases and Deployment Scope

We use Zeplin to help us implement mockups for Users Interfaces in our games and on our websites. It is used mainly for the first prototypes in a simple way, focused on the handoff of the design side that can be picked by programmers after. It helps us iterate quickly on those ideas and design good UI and UX.

Likelihood to Recommend

Zeplin is well suited for teams that want to organize the development workflow of web apps and user interfaces in a way that the design team has more control and can pass information in a better way to the developer team. If your team is small or the web app or product being created is not so big, maybe other options that do all the mockup/wireframing/prototype in only one tool probably will be better.

Use Cases and Deployment Scope

Zeplin is being used between several departments and in collaboration with clients. It's primarily a valuable piece of software for our design department who can share and create designs and style guides with our project managers. It's a great tool to work alongside Adobe and Sketch etc. The collaboration between the apartments is the key to success here. The rest of this review will be written from an IT point of view.

Likelihood to Recommend

Zeplin is an excellent tool for collaboration between departments. Designers, developers, and project managers. From an IT point of view, we'll find a manageable user interface where we can encourage our end users to invite clients where they work as an Alien. If they need more than viewing access, we can set it for them quite easily. I would have loved a more natural way to integrate the access with other IT systems together with a better definition of user roles.

Use Cases and Deployment Scope

Zeplin acts as a bridge between the design teams and developer teams to assist in the handoff of the finished design artifacts. Once the design is done, it is exported to Zeplin and Zeplin parses the screens to enable assets and delivers specifications to the developers. This relieves designers to manually deliver the assets in multiple folders or files and explain those to the dev team. Zeplin saves a ton of time in manual work and makes it easy to update the assets when the design changes.

Likelihood to Recommend

Zeplin helps with asset management and design artifacts delivery. It enables conversations like InVision with its commenting features. It can help maintain collections of design works in custom sections. Various inspection features support the developers to build pixel perfect interfaces. This is not useful for clickable or rapid prototyping. It is only helpful as an archive bridge between design and development.

Use Cases and Deployment Scope

We use Zeplin between two departments ( content and tech ). For the tech team to show off their best work, we need to know what the desired results are to be displayed. With Zeplin, the tech team can collaborate with the content team via notes directly on the mock-up. This is ideal for questions and answers that will not get lost in the shuffle, but rather are pinned directly where the question stems from ( point on the design ). This allows for very minimal miscommunication.

Likelihood to Recommend

Zeplin is well suited for web developers to understand what the marketing team is desiring. For me, Zeplin is the desired resulting display from the code that I am writing. Zeplin takes the guessing of styles, guessing of size scale, out of the equation. Zeplin would be less appropriate to use if I were a beginner web developer, as it does not include any actual code ( other than styles ) in the project.