Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing jQuery Mobile vs React Native, the Slant community recommends React Native for most people. In the question“What are the best frameworks for developing cross-platform mobile apps with JavaScript?” React Native is ranked 2nd while jQuery Mobile is ranked 13th. The most important reason people chose React Native is:
React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper.
Question 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 Allows you to develop native apps
React Native allows you to create native apps by generating native views with JavaScript instead of using a web wrapper.
Pro Large, supportive community
Despite being such a young framework (early 2015), the support for React Native grew quickly. There is a forum, active tag on Stackoverflow and many other ways to get help from the community.
Pro Backed by Facebook
Facebook writes their mobile apps in React Native so the code base gets pretty thoroughly used in some highly demanding scenarios.
Pro More predictable control of the state
The one way data flow, makes it more predictable and easy to control.
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 If core team doesn't use a certain feature, it's not developed
Whenever there's functionality you need that they don't use in their apps, it's not going to get developed by them, even if it's obvious it should be in the core. They always say to either submit a PR or create a separate module.
Con Steep learning curve
React Native is not the most beginner-friendly framework for creating mobile apps with JavaScript. It requires that the developer know React, which is known to have a steep learning curve.
Con Many existing JS libraries are not usable on React Native; not exactly a 1-to-1 experience to writing React either
Example: Library that provides a full calendar with agenda view.
In the end it's much easier to develop in actual JavaScript with a solution such as Ionic, especially if your app needs to work well on the desktop.
Con React native only supports react which is getting old
React native is only based on react which is getting old. An old tech developer can't take much breaking changes so it gets more patchs. There is a limit, and react is too verbose and complex. better alternatives available today.
