Following are the pros and cons of Polymer JS
It ensures a work balance between the designer working on Web page UX and developers who are more concerned with the Web page functionality. With the help of polymer elements (themes and designs), developers don’t have to modify complex web page source code to match the designer’s specifications.
Compared to React, Polymer JS doesn’t have much to offer, probably the reason why many of the developers don’t opt for it. Another is Angular2, which serves as an alternative to Polymer JS and both React and Angular2 enjoy a bigger community than Polymer JS. These aren’t the only ones that can be compared with Polymer JS but definitely the more popular ones. It isn’t likely for developers to choose Polymer JS leaving the above-discussed because of the constraints of Polymer JS that will be discussed later.
Whereas, it is used on the Google websites such as Youtube, Google play music, and few others. Youtube is entirely developed using Polymer JS and the Chrome settings page is Polymer JS too.
PolymerJS on paper has an appealing approach but it is an idea that is ahead of its time. Polymer JS places several components requirements on the browser relying on technologies that are still in the process of standardization (by W3C) and are yet to be integrated into the browsers. Examples include the shadow dom, template elements, custom elements, HTML imports, mutation observers, model-driven views, pointer events, and web animations. These are great technologies but for now, aren’t available on modern browsers. The polymer is based on the strategy to have front-end developers use these still-to-come technologies that are currently in the process of standardization (by W3C) as they get launched on these browsers.
To make it easy to comprehend, the Google polymer theoretically is relying on technologies that are yet to come to these browsers. Polymer JS serves as an example of how element-centric applications can be built in the future (when the browsers get all the necessary features and dependency on polyfills ends). For now, Polymer seems like an interesting concept but not a practical one to be used for creating robust and dynamic applications which is why you might not come across a Polymer tutorial outside of Google documentation.
Considering the newness of Google Polymer as a technology, novice app developers might find it a bit brittle because of some of the findable rough edges.
You will encounter dependency errors that point to the different version dependencies even in the same elements even when you download the polymer.js elements as recommended. It has been established already that Ploymer.js is currently under development regarding the element’s issues but it can make development challenging thus might put off developers to work with it.
The performance of Polymer JS on mobile phone platforms is nothing short of a frustrating experience.
Polymer JS is an interesting technology but it still is in the development stage and not fully functional. It can’t be relied upon to develop large-scale enterprise production-ready applications as of now but once it gets completed then the story can differ exponentially. Other than this, there aren’t many guides and tutorials available explaining the working of Polymer JS.
Polymer makes some convincing arguments but the opposition to it exists and can’t be sidelined. We will have to wait and see how it is going to perform when it’s all done.