HCL Domino vs. Ignite UI

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.

Incentivized

Angular is our framework of choice for a number of reasons. Business data is almost always displayed in a grid format. It makes sense to start with a strong widget that is powerful and fast when building applications. Ignite UI provides a complete toolset of widgets for other frameworks, but Angular is our focus. Ignite UI is helping us deliver a great UX/UI.

Incentivized

• Domino support for policy-based user registration and deployment eases end-user creation.
• User access to databases is simplified via group membership and defined roles.
• Email replication to clustered servers is simplified through connection/replication documents stored centralized address book
• Group calendaring enabled at client level controls.

Incentivized

• The examples are great and close enough to real-life usage to be truly helpful
• The OOB configuration and themes are good. They are very configurable.
• The touch support and response web are built in, allowing the same code to work well on desktop and phone.

Incentivized

• User interface needs to be modernised.

Incentivized

• I would like to see examples with security tokens. It really isn't an Ignite UI issue, but would be helpful.
• Some of the examples are over-simplified, not how the products would be used in real life.

Incentivized

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.

Incentivized

We tried DevExpress when we started a project a couple of years ago. At the time, the documentation and ease of use went to Infragistics. When trying new or updated tools, the documentation and samples are everything. Having minimal documentation or documentation that seems to be written for people that already know how to use the product is just plain frustrating. Samples need to be something close to the real-life usage of the product.

Incentivized

• 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.

Incentivized

• There is a learning curve, of course, but the comparisons between the projects with and without Ignite UI are worth it.
• The time savings on development is very real. The built-in functionality is amazing.
• We are able to focus on features rather than getting the look and feel of our deliverable.

Incentivized