Coda, from Coda Project headquartered in San Francisco, is a template-based document generation solution, supporting a variety of use cases presented by the vendor as ideal for smaller companies that might otherwise be relying on spreadsheets to maintain (for instance) product development, or inventory tracking. It is available free, with paid editions to support teams, automations, or for more advanced collaboration and workspace features, as well as more advanced security features.
$0
per month
Zeplin
Score 8.3 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.
$0
per user per month
Pricing
Coda
Zeplin
Editions & Modules
Free
$0.00
per month
Pro
$10.00
per month per doc maker; unlimited editors (paid annually)
Team
$30.00
per month per doc maker; unlimited editors (paid annually)
Enterprise
Custom Pricing
Free
$0
per user per month
Team
$6
per user per month
Organization
$12
per user per month
Enterprise
Contact sales team
Offerings
Pricing Offerings
Coda
Zeplin
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With Coda, you only pay for Doc Makers.
Often one person creates a doc, others edit it, and some simply observe from afar. Instead of charging for everyone, we only charge for the people who create docs.
Interested in enterprise pricing? Visit coda.io/enterprise
My organization considers Coda for a variety of business and organizational projects. Using Coda, my organization keeps a lot of data and different types of data in one place. The user interface of Coda is very fluid and easy to use. My organization has benefitted from using the efficient and effective operational functionality of Coda.
Zeplin is, overall, really great for what it’s known for: design handoffs to development teams. Thus, it’s an excellent tool for scenarios in which the design and development teams do not work very closely. Because it allows users to use the tool on various platforms, it’s also great for teams in which there are in-house and remote (or contract) staff working on a single project. The tool is pretty lightweight once users are on-boarded, so it’s also great for larger teams. However, it can take significant time to onboard people to it, so it might not be great for more rushed projects. It also doesn’t have a ton of functionality beyond supporting design handoffs, so one might choose a more inclusive tool, such as Figma, to support more steps in the design process. Finally, Zeplin is costly and its rates are pretty inflexible, so this might not be the most ideal tool for more cash-strapped teams who want to use Zeplin for more than one project at a time.
It takes getting used to in terms of how the formulas per column is implemented, in contrast to how we build tables in Excel. For organization/team purchase, it would be worth considering having a training for the core team of users. Right now, we do a lot of self-learning.
Inability to email charts or image without these objects being hosted on a third party. The community has been great in providing workarounds but it would be much more convenient to be able to have such ability natively.
APAC Support. I'm based in Malaysia, due to timezone differences, even with a livechat implemented, the support for each step and conversation takes up to 24 hours per response. Having some hours covered in our timezone would greatly improve customer support experience.
Coda is definitely something that has been proven to drive positive impact in our organization. We have many divisions that can benefit from this that we have yet to explore. It would definitely be worth renewing.
Coda can seem either really useful or really useless. The extremes of both ends is driven by what our own understanding of what we want to implement. If we lack this understanding, it will be easy to misunderstand Coda's usability especially in the wrong context.
Zeplin is not a fully functional prototyping software system, but having the ability to add notes to help explain what actions are expected allows me to rate it high.
We haven't done any integrations - the initial part of our experience we found that for docs with complex formulas, the page tends to load slowly but in recent months, Coda has improved and optimized the loading times in general and we generally don't find any problems in terms of speed anymore.
Mainly due to timezone differences. I think Coda's support in general is well implemented and executed. They know their stuff and are helpful. But since I'm not in the same timezone, solution rates are slower for me, and that's not something I prefer. I work in customer service, too, and more often than not, time is important. Shortening the solution time would be a much greater experience.
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'm relatively inexperienced but this experience is meaningful. It would have been nice to have some guidance from Coda so that we understood more on Coda's purpose and potential.
While all of the products listed have great features and platforms, there was always one thing missing from them that I would need to get from another application. Coda was the first one we used that really combined some of the best parts of those products and allowed us to use it in one place. I also appreciate the flexibility of creating your own framework and workflow, unlike in other tools where you have to follow how they capture data and organize projects.
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 think scalability is definitely good here since it's based on number of doc makers. Implementation into each dept becomes simpler. That being said, due to the nature of our work, we find it easier that we have a "super user" and then a team of other doc makers. This would make the doc creation and management more efficient.
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.
