HCL Domino vs. Swiftify

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

It is recommended to use Swiftify in any situation that requires iOS development because even if you develop just in Swift or just in Objective-C, it could be helpful for researching and investigating purposes. Additionally, if you need to convert big quantities of code from Objective-C to Swift, this tool will optimise that work. It will not translate a whole class of 2000 lines perfectly, but after converting it you can review the code and modify the lines that have not been properly converted, making you save more than the 50% of the time in that case. I've not been able to test it properly as I only used the trial version and it is really limited.

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

• Helps to prevent redoing the whole code.
• Sometimes it is hard to find the exact command of Obj-C in swift.
• It helped me to learn more :)

Incentivized

• User interface needs to be modernised.

Incentivized

• Sometimes the conversion doesn't make much sense. The Swift conversion doesn't compile, or is not optimized.

Incentivized

I don't have any problems with the platform. I like that their email responses are fast.

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

There's not much to compare - we haven't found any proprietary like it. Existing OpenSource solutions are unmaintained and Swiftify supports the latest versions of Swift.

• 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

• For now the impact has been small, considering that I used the trial version, it was helpful for small conversions. Summarising: Saving time on researching process

Incentivized