AppMaster.io vs. HCL Domino

Best suited for complex apps with different business flows that you have to join in one product. Also perfect for enterprise apps with a single backend but different types of users (like clients and account managers). The built-in deployment options let you run your app offline, which is great for highly secure apps with sensitive data. Also good if you need API integrations - docs are ready-made and there're many pre-set modules. As for less appropriate scenarios - AppMaster.io maybe be too rich for simple single-button apps, but once you move past the entrance threshold, simple apps are just several minutes away with AppMaster.io.

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

• Server back end nocode businnes processes create
• Visual programming
• iOS/Android APP development
• Admin panel

• 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 service is rapidly developing now and adding new points constantly, so hardly any specific weaknesses can be pointed out.

• User interface needs to be modernised.

Incentivized

Very quick replies, very thorough answers, they help with even the smallest cases and always are there when you have even the most stupid questions.

Wide functionality allows you to implement complex projects. The server back-end is very easy to communicate with applications. And there are a lot of additional integration modules with external services.

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 can develop faster with a smaller team.

• 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