Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing jQuery Mobile vs Polymer, the Slant community recommends Polymer for most people. In the question“What are the best frameworks for developing cross-platform mobile apps with JavaScript?” Polymer is ranked 11th while jQuery Mobile is ranked 13th. The most important reason people chose Polymer is:
It provides a base component.
Specs
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 Various basic components
It provides a base component.
Pro HTML markup is not string
HTML markup as it can be a non-string.
Pro Flex layout components
It provides Flex layout components.
Pro CSS is easy to apply
CSS can be applied far more comfortably than React.
Pro No need for special debugging tools
The presence od specialized debugging tools are advertised by competitors. The all features of web components are natively supported by browser embedded development tools.
Pro Excellent routing
The router is embedded into CLI for project creation and covers as web as Progressive web app, also fused with Polymer layouts out of the box. The shop template for CLI has a complete solution including the routing.
Pro Complete web app stack support
Full app stack from data tier to routing, progressive web app, responsive layouts makes no need to seek outside of Polymer ecosystem for application features.
In addition to waste set of mature web components in Polymer Elements along with Vaadin Elements there are thousands of web components in the wild comparable to jQuery plugins set.
Pro Excellent documentation
Polymer guides you as with tools (cli, build environment, app templates,..) as with complimentary documentation on all phases of app development from creation of app as progresive web app to production deployment instructions.
As Polymer is standards based, the whole community around those standards also helping in documentation and support.
Pro Based on web components
Web Components are a collection of specifications released by W3C as a way to reduce the complexity of web apps by creating reusable components. Browser support is currently poor for web components, however Polymer is developed to make web components compatible with modern browsers.
Pro API is easy to understand, based on standard
The Polymer APIs are split on application layers and follow standards on all possible ways: Web Components, CSS variables, async API via Promises and so on.
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 No server-side rendering
Polymer does not support server-side rendering. This results in higher loading times, more HTTP requests and it's not very SEO friendly, since search engines have no way of indexing a page if it's not rendered in the server.
