When comparing jQuery Mobile 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 jQuery Mobile is ranked 13th. The most important reason people chose NativeScript is:
Used by Svelte framework for native development.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Resources
With HTML5 development being relatively amateur jQuery Mobile has a vast selection of resources to assist. These resources include websites, books, apps and other frameworks, 3rd party plugins and extensions, and more. All of these can help ramp up and excel the project development cycle.
Pro ThemeRoller
An interactive tool that has been created to customize an apps theme. Users can import a current theme, make changes, and export the theme back to the app for integration.
Pro Download Builder
To optimize application development jQuery Mobile provides a tool to allow the user to customize the framework. It contains the ability to pick and choose which modules to include and then bundles the framework so it contains only what is needed.
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 The project is practically abandoned
The last release was in 2014. Samsung Tizen Advanced UI (TAU), for example, was started with JQuery, but it was forked off and completely rebuilt from scratch with jQuery concepts but without JQuery dependency itself.
Con Clunky and slow
Con No MVC support
There is no included MVC support in jQuery Mobile. It is possible to achieve this, however, using other frameworks such as BackboneJS in combination with jQuery Mobile, but there are a few limitations. Specifically that MVC frameworks, such as BackboneJS or KnockoutJS, are not compatible with jQuery Mobile page routing.
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.