1. The whole design guide is not implemented (date picker for example)
2. Web components polyfill while pretty fast still slows things down a bit
3. Extra effort required to debug/style components (shadow DOM)
4. It's still fairly bleeding edge, not for the faint of heart
5. Vulcanizing required for assets to avoid hundreds of imports/requests
These are some of the factors that would make me reconsider using it on another project. It still turned out very nice for the project however.
I want web components to be a thing but Polymer is not the path forward in its current state.
The blog post mentions speedups in Chrome and Safari. It does not mention Firefox.
You don't have to do anything special.
1. import polymer html file 2. use it
thats all there is to it.
If you use the newer, lighter-weight shady-dom version of the polyfill, which is a lot more responsive on non-Chrome browsers and doesn't introduce the bug indicated in [1], you must do all DOM manipulation via polymer's local DOM api, in order to properly distribute dom elements.[2]
That means, if you want to use polymer, you cannot use angular or ember (for example). Specifically, DOM manipulation via those libraries ends up just using regular calls against element.appendChild, but those appended elements, if they are polymer elements, end up not properly working (event listeners don't attach and styling modifiers don't apply), because you didn't use polymer.dom to go via polymer's local dom API.
I found out about all of this the hard way, and now I have a webapp that works great on chrome, but users cannot use the rich text editor on anything except chrome. Which eliminates all iOS browsers entirely.
1: https://github.com/webcomponents/webcomponentsjs#execcommand...
2:https://www.polymer-project.org/1.0/docs/devguide/local-dom....