DevExpress Universal vs. HCL Domino

When you want to display spreadsheet based reports, it's really convenient as it has everything out of the box.

If you have very basic components like combo boxes or lists, there is hardly a point in using such a large component set.

In the end, it's a matter of finding a good balance between functionality and complexity.

Incentivized

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

• Handle large and complex datasets using its table widget (DataGrid)
• Handle large and complex hierarchical datasets using its tree table widget (TreeList)
• Customize widget to fulfill advanced requirements such as adding a complex grid inside a grid cell

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

• Documentation could be improved
• Better examples of code in languages other than C
• Better wizards for building applications

Incentivized

• User interface needs to be modernised.

Incentivized

DevExpress Universal controls are much simpler to use, implement and customized as compared to Kendo. Learning curve for telerik is high, though level of customization that can be achieved with telerik exceeds that of DevExpress Universal. Found DevExpress Universal community support to be better then its competitors. License cost is also a wining bar here.

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

• It is good for asp.net application and it takes less time in development which we used two years back.
• We have stopped with these tools when clients were asking applications to be built in angular or react. We have switched to Kendo.

• 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