HCL Domino (formerly IBM Domino, and before that Lotus Domino) is an enterprise application development platform, boasting mobile-app capabilities to enterprise authentication and a companion low-code app builder called Domino Volt.
N/A
Zeplin
Score 7.9 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.
Domino is best in medium-sized businesses of 20-100 employees. It's too complicated to implement in very small companies unless you have good external resources. It scales up very well for larger companies but the pressures of users wanting particular "brand-name" software can become difficult. If you want a restricted "extranet/portal" system for a limited set of members it's a great system, particularly if you add a Domino CRM on top. Unlike Microsoft, you never have to resort to command-line tools, like PowerShell, in Domino to get things done.
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.
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.
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.
We use SharePoint, SQL and Teams but only for the things that they excel in. For example, we use teams for small team interactions (including external participants). We use teams for meetings too. We've discovered that Teams collaboration is not as full-functional as Domino and more importantly, that our members (financial services) do not trust the Open Office365 cloud. SharePoint and Team collaborative features are often blocked in our member organizations. Domino is much easier to identify and unblock at the firewall level. It's much easier to restrict collaboration to approved options in Domino.
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.
The immediate impact on my organization as a non-profit is cost. Enterprise pricing for a Domino solution is exponentially more inexpensive than more popular applications.
Of the most obvious impacts is user familiarity. Given a vast majority of the employment pool having familiarity with MS products, orienting new employees to Domino\Notes is burdensome. Adoption is slow and resistance is high.
Hiring Domino administrators and developers is increasingly challenging.
The recent sale of the Domino platform away from IBM is concerning.
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.
