Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$15
per month per editor
Zeplin
Score 7.5 out of 10
N/A
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.
$15
per month
Pricing
Figma
Zeplin
Editions & Modules
Professional
$144
per year
Organization
$540
per year
Starter
Free
Free
$0
up to 1 project
Advanced
$15
per month per seat (up to 50 projects)
Basic
$15
per month per project
Enterprise
Contact sales team
Offerings
Pricing Offerings
Figma
Zeplin
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Figma
Zeplin
Considered Both Products
Figma
Verified User
Professional
Chose Figma
Figma has more features than Zeplin or Axure. Unlike Zeplin it allows to create and share dynamic prototypes. Unlike Axure it gives tools to create detailed designs.
Figma compares to these other software packages as it seems to combine the best aspects of each, whilst simplifying its own interface to make usage more intuitive. Although Illustrator is still excellent for vector illustration work, and Sketch does appear visually fairly …
Figma enables people to create designs AND collaborate. The difficulty of keeping all of the feedback on a design in one place (or tracking it down!) can be difficult when working with other programs, and Figma facilitates the ability to have streamlined feedback loops all in …
Zeplin is simpler. Zeplin lacks prototyping on par with InVision. Zeplin doesn't give a direct code for Android and iOS like Figma does. Zeplin doesn't have a lot of advanced features like InVision, for example, whiteboard. But Zeplin is good for at its job which is to share …
Actually, we didn't select Zeplin. After a long time of internal discussions, the majority of the team decided that we want to move to Figma. We still use Zeplin as a legacy, but we don't use it for new features. In my opinion, it's less flexible than Figma, which allows …
Zeplin is used for us purely as a handoff tool. It keeps it clean and clear for devs and product managers what is completed. It has some good labels and other organizing features. The different levels of access are also super helpful to give the correct people the view they …
As our project is large and there are many modules and they should be consistent. So, Zeplin's style guide can be shared globally across different projects and we can easily ensure consistency across all modules. Zeplin automatically exports assets in multiple file formats like …
Zeplin is more focused on the handoff than in the creation itself. The other alternatives can do both, but Zeplin is an awesome tool for the handoff part. It depends in how big is your team and how the workflow is organized to understand whats the best tool for your team.
Out of all of the products that I have used to support design-to-development handoffs, Zeplin is my favorite. It’s pretty lightweight and easy to use (once you get the hang of it). Zeplin also has a smooth interface and is, generally, clearer to use than other tools, such as …
I would recommend if you need to start from scratch a product UI or any customer journey that you need to implement that requires designing and visualizing different steps to complete a process. I would recommend that any design/UI/UX team brainstorm and make proposals that they can compare and discuss in a visual way.
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
Figma allows us to create universal content. This means that if multiple designers want to re-use a piece of content, and if everyone's content should be dynamically updated from time to time, we can easily accomplish this by turning design elements into a universal instance. Then, if an update is needed, we can push the change out to all assets at once. It's very efficient and ensures we're all updating content accordingly.
Figma also allows us to set parameters for the company's brand guide and share them across various designers. This way, we can easily pull from approved brand fonts, colors, and more, which allows our assets to remain unified across multiple touchpoints.
Figma also allowed us to create and install our own plugin, which we use to export every slide we have in a frame at one time, versus the default export feature, which limits you to one slice at a time. This is particularly useful for us when we're working on email templates, since we tend to have a ton of slices in any given series.
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.
It will be great if Figma will consider having the Pages where interactions can be stitched together among the Pages and not just one page with so many Frames to create the stand-alone clickable prototype that can be used to simulate the intended UX
Bring back the Inspect Mode tab right on the right-side panel of the main workspace instead of hiding behind the Dev Mode.
Figma Slides feature could be improved quite a bit more in order to be easier to assemble slides into a presentation deck and having pre-built templates for slides can be useful too.
Figma is a pretty cool tool in many areas. My team almost uses it on daily basis, such as, brainstorming on product/design topics, discussing prototypes created by designers. We even use it for retrospectives, which is super convenient and naturally keeps records of what the team discusses every month. Furthermore, I do see the potential of the product - currently we mainly use it for design topics, but it seems it is also a good fit for tech diagrams, which we probably will explore further in the future.
There's a bit of a learning curve, but generally I think it's both more powerful and intuitive that other UX design tools. Most of what I need to do as a designer can be done in this platform, from basic wireframes to creating a design system, to creating pixel perfect designs, to prototyping to dev handoff.
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.
I haven't used their support lately but in the past, they had a chat that I used often. They often responded in a few hours and were able to give a satisfactory solution. I would imagine it's less personal now but the community has expanded drastically so there are more resources out there to self serve with a bit of Google magic.
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.
In-person training has its own benefits - 1. It helps in resolving queries then and there during the training. 2. I find classroom or in-person training more interactive. 3. Classroom or in-person training could be more practical in nature where participants can have an hands on experience with tools and clarify their doubts with the trainer.
Online training has its own merits and demerits - 1. Sometimes we may face issues with connectivity or the training content 2. The way training is being delivered becomes very important because not everyone is comfortable taking online training and learning by themselves. 3. With the advancement of technology online training has become popular but there is a segment of people who still prefer class-room training over online one.
Miro is more user-friendly than Figma, but is less robust in terms of web prototyping and graphic design. While Figma isn't made to be used as a design tool, our team has taken to using it as such because it's richer in functions and personalizations compared to Miro and Figma.
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.
