Likelihood to Recommend 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.
Read full review Progress Software Corporation
I gotta be honest, after a PoC period, we choose to rewrite the whole application in a different cross-platform app. Our developers had to invest a lot of time and effort to debug a lot of plugin-related issues, which we needed to utilize the android mobile phone capabilities. QR reader, special visualizations, and fine-tuning were really hard and often resulted in writing native Android code instead of using the shared Angular code. In the end, we think that writing a standalone Android app and an Angular app would have been a better alternative, as the shared code base was so unreliable that it did not save us any time.
Read full review Pros 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. Read full review Progress Software Corporation
True native app. The app uses native components and that is quite noticeable in the overall performance of the app. NativeScript is also awesome in the way we can access the native APIs, so we are never really constrained by the framework. If we need, we can just dive into the native APIs without leaving our environment and language (JS). Cross-platform. Builds for Android and iOS. It deals with the platforms differences very well. Support for Vue.js. Even though it is just a community effort, the NativeScript-Vue plugin is the best alternative to build native Apps with Vue.js. That was a major factor to go with NativeScript. Read full review Cons User interface needs to be modernised. Read full review Progress Software Corporation
The need to know the native Android and iOS APIs to access device hardware and other platform-specific functionality Not all user interface components are available for free NativeScript has no HTML and DOM, which requires some deep knowledge of different UI tools to be implemented instead Read full review Likelihood to Renew Progress Software Corporation
The hybrid is ok but native is better for performance and the right use case I want to go for is the performance without dealing with too many development tools.
Read full review Support Rating Progress Software Corporation
The community support is excellent. They have a slack community as well as a discourse forum forum.nativescript.org Both of these offer community driven support. The forum is more for a threaded discussion. The slack community is more for a quick talk.
Read full review Alternatives Considered 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.
Read full review Progress Software Corporation
Ionic Ionic is an excellent Angular-based framework for mobile, and it does give a lot of access to the native device api's. However, the technology is based on Cordova, which means the apps being built are just webviews, with html, css and JS all running on the UI thread, and potentially creating very slow experiences for users. NativeScript is a truly native solution, and so provides a faster user experience. ReactNative We evaluate ReactNative, and found it much the same as NativeScript. The main difference is that your JS is all written with React, while NativeScript lets you choose between normal JS, Angular, and Vue. For our team, Angular was the most appropriate choice.
Read full review Return on Investment 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. Read full review Progress Software Corporation
The poor quality of NativeScript documentation has the potential to weigh heavily on development timelines, budgets, and QA resources in a NEGATIVE manner. The poor interoperability of NativeScript plugins can significantly increase development time. The need to seek out professional instruction to learn how to use NativeScript effectively may become a burden on your budget. The number of breaking changes between versions of NativeScript, may cause your development efforts to lag further behind the most recent releases of NativeScript and your other chosen environments than you are accustomed to. NativeScript still does not support the latest major version of Angular. Any significant changes to the other environment components of your systems may hold you back even further while NativeScript plays catch-up. Read full review ScreenShots