Slack is a group messaging or team collaboration app that aims to simplify communication for businesses. Features include open discussions, private groups, and direct messaging, as well as deep contextual search and message archiving, and file sharing. Slack integrates with a number of other tools, such as MailChimp, Dropbox, and Google Drive. Slack was acquired by Salesforce in December 2020.
The product is free to use, and also has paid plans with more features and greater controls.
The…
$8.75
per month per user
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
Slack
Zeplin
Editions & Modules
Free
$0
Pro
$7.25*
per month per user
Business+
$12.50*
per month per user
Enterprise
Contact Sales
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
Slack
Zeplin
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
*Per active user, per month, when paying once a year.
Pro is $8.75 USD per active user when paying month to month. Business+ is $15.00 USD per active user when paying month to month.
—
More Pricing Information
Community Pulse
Slack
Zeplin
Considered Both Products
Slack
No answer on this topic
Zeplin
Verified User
Professional
Chose Zeplin
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 …
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 …
These other tools are really helpful products for creating and sharing wireframes / prototypes. However, Zeplin is the best tool for the actual hand off between the design and development teams once the design is actually ready to share. Zeplin fills this gap and improves the …
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 …
Zeplin is a really nice lightweight app, that is easier to use than InVision for sharing purposes. InVision does primarily handle prototyping, which Zeplin does not do. Abstract is my product of choice but is also a slightly different tool — almost a GitHub for design. It …
Slack is great for tracking commits to new coding projects. You can take parts of code that still need to be implemented later and easily search through the history of comments if there is something that goes wrong with a code commitment. It can be difficult for people that only like Teams to adjust to a new platform if you are using both to communicate.
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.
Would love a better integration with GitHub. For example, notifications when your PR is updated, when review is requested, @-mention in comments, etc.
Improved "Later" tab, for example the ability to create to-do lists or making the "Later" tab into a more powerful to-do list (annotate items with notes)
More powerful integrations, e.g. Google Calendar could render a calendar view within Slack, rather than sending the daily schedule
To be more transparent, I give 10 because Slack serves our collaboration needs. It provide us a good platform for team communication relaying important update within the company, it has even mobile app where you can install in your phone to monitor any updates within that team that needs your immediate attention and intervention.
My rating was 7. Its intuitive interface and user-friendly features like channels, threads, and integrations make it excellent for team communication and onboarding. However, its usability is held back by the resource-intensive desktop app and cluttered feeling in large workspaces. The mobile app's performance and unreliable notifications have also been noted as weaknesses.
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.
Yes, the app works 24/7. I don't even recall having any period that we could not use since the implementation. Even the maintenance periods are barely noticeable and our work is not impacted by it when it happens.
Slack is a soft app, we don't have many issues with it. I recall one or two people complaining about something during our usage period, but I didn't have a bad experience. When the app is slow, usually the problem is with my computer or my internet. The app works just fine.
Whenever I've had to troubleshoot an issue with Slack (which, to be honest, has not happened very often), their online documentation has been easy to locate, easy to understand, and effective in resolving my issue. Slack's ever-growing popularity also means that there's a large community of practice out there that can be depended upon.
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.
I like Slack better than ClickUp, because I would spend 30-60 minutes a day updating my ClickUp tasks. The way ClickUp was used was very micromanaging. I billed by the hour, so I was willing to put in the time to alert the boss what tasks I was working on.
One of my jobs used Hive - I mostly just ran it in the background in case anyone messaged me. I did not use it often.
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.
Slack has been incredibly helpful in connecting various tech apps and ecosystems, creating a more streamlined and responsive process.
Slack has made it significantly easier to communicate with our team members across multiple time zones, creating a more engaging environment for our all-remote team.
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.
