It provides a base component.
Ranked in these QuestionsQuestion Ranking
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.
Pro Real device deployment
Connect your PC and mobile device through Wi-Fi using Tabris CLI - and just hit the Refresh button in your application to see the latest code version in action. No emulators or attempts to run a mobile application in the browser.
Pro Cordova plugins support
Most Cordova plugins work with Tabris as plug-n-play modules, without any special tuning.
Tabris is very easy to use. You can just download Tabris Dev App from Play Store/AppStore and run any example from GitHub or code snippet from documentation right away using Playground. Documentation is easy-to-follow, and to start developing in your local environment you should only download lightweight CLI tool that will pull application code from your PC to mobile device using Wi-Fi.
Pro Native widgets instead of web views
Tabris using native widgets - it makes your app run faster and look...native - regardless of platform. Stop trying to make your buttons look "like real iOS buttons" when you can just use the native ones.
Pro Completely free
Framework and all required tools are free. Playground and Dev App - free. Online build services -for free. For some time local build service was under a paywall, but now that feature is also free for everyone.
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.