When comparing Kendo UI vs NativeScript, the Slant community recommends NativeScript for most people. In the question“What are the best frameworks for developing cross-platform mobile apps with JavaScript?” NativeScript is ranked 5th while Kendo UI is ranked 7th. The most important reason people chose NativeScript is:
Used by Svelte framework for native development.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free Core tools
Kendo UI is separated into a commercial and open source frameworks. The core of Kendo UI is in the open source frameworks, but some usability and benefits of Kendo UI are lost without the commercial version.
Pro Platform-based UI
Kendo knows what device it is being viewed on so it can adjust the UI accordingly. If a user is on a PC the user will see things differently than on a mobile device. Between iOS and Android the user will also notice a different as it pulls from the core UI of those core systems.
Pro Theme Builder
An interactive tool that has been created to customize an apps theme. Users are able to select from many pre-defined themes, edit them, and download the theme to bring into a project.
Pro Svelte Native
Used by Svelte framework for native development.
Pro Leverages knowledge in Angular
Angular is a very popular framework, and teams already developing angular will feel right at home with Nativescript + Angular
Pro Works great with vue.js
Cons
Con Expensive commercial tools [$699, $1,499]
The other core tools developed with Kendo are the commercial tools. There is the Professional version for $699 that will result in more jQuery UI widgets and client support. The $1499 "DevCraft" Complete edition gets developers the DevCraft .NET toolbox, testing and debugging frameworks and applications, as well as priority support.
Con Nativescript + Angular apps for Android tend to have long startup times.
It's very difficult to have acceptable startup times with NS+Angular in Android. It's not uncommon to see apps taking 6 sec or more to start AFTER having been optimized with Webpack (mandatory!). The same app in iOS takes only 2-3 sec. Also, this seems to happen only with the NS+Angular flavour. People using plain NS (without Angular) don't seem to have the issue.