Progress Kendo UI vs. NativeScript

It allows us to extend the components or create new components in an easy way. The control suite is complete and powerful enough that you do not need to consider other competing packages. The controls are relatively easy to implement and when we ran into problems the documentation and online support were very reliable.

Incentivized

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.

Incentivized

• Kendo UI controls provides rich set of features and capability that is required for enterprise products.
• Performance of controls are satisfactory overall though few other vendors provides extraordinary performance for specific controls and for specific purpose. Kendo UI provides most of the required controls and with rich feature that made us to select Kendo UI controls for our development.
• Kendo UI controls quality, in terms of performance, robustness and well defined interfaces are very positive notes.

Incentivized

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

Incentivized

• Kendo UI is always moving forward and staying current with latest development trends. While that is beneficial, that can cause some issues when supporting customers (particularly government) that don't move their IT infrastructure along nearly as fast. A prime example is web font icons. Great and easy to use, but where Kendo UI utilizes web font icons as the sole means of displaying an icon, not all organizations (again, especially government) allow the use of these. There have been times where Kendo UI became unusable and we had to downgrade to a version a few years old. Makes continued payment for licenses sometimes feel wasted as we may not be able to always use the new releases
• Kendo UI has a wonderful feedback system and they do indeed listen to the community. However, there do seem to be some instances where there is large support for a new feature/component and it never gets addressed. It is easy to understand that not all ideas are easy or even prudent to implement, but would be nice to see a better follow-up on ideas with a current status
• Refreshing Kendo UI grids is simple, yet the standard API method causes the grid to return to the default state. We have many use cases where we would love to update the grid data but need current grid state (such as expanded detail rows, sorts, filters, etc) preserved after the grid is updated so that users do not have to perform grid actions again to return to the desired state.

Incentivized

• 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

Incentivized

Nothing better has come along. I'm always on the lookout for new UI libraries and I have tried most of them. Kendo has done a good job of keeping my business. They aren't perfect, but no one has done it better as far as I can tell. I'll keep a look out and my rating may change in the future if they get complacent.

Incentivized

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.

Incentivized

it's easy to implement in applications. The kendo widgets are able to be used in almost any type of business application which has a UI. For most part, once the developer has completed a project which uses Kendo, many time code can be copy/paste into a new application. Kendo UI documentation keeps improving so finding the answers to questions can be easy

Incentivized

The errors that we have detected were not of great importance and the online support provided a temporary solution until the next release.

Incentivized

Reports sometimes take a bit of time to load

Incentivized

Overall, we are satisfied with the support offered by the Progress Kendo UI team. We had raised few helpline incidents in the past and they have been resolved timely by the team. Also, we were satisfied with the level of information and support provided by the team.

Incentivized

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.

Incentivized

it took me about one day to make the components available for all the team members, including a quick demo, parallel setup in everyone’s workstation and packages deployment into our nuget server after 3 days of one to one support, everyone was able to use the components or find help in the documentation or resuest support

Incentivized

At the time of our product selection we identified better cross-browser compatibility and we estimated that turnaround for support was superior. At the time, the vendor had a higher positive feedback footprint among their user community.

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.

Incentivized

Never faced a problem even when we threw a large amount of data at it

Incentivized

• Kendo UI has saved us a ton of time in development.
• We were able to get certain things to market faster due to the fact that we didn't have to piece multiple libraries together like is so common with modern web development.
• Because of the price of the library, however, we have not been able to purchase upgrades every year.

Incentivized

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