When comparing Tizen vs Polymer, the Slant community recommends Polymer for most people. In the question“What are the best frameworks for creating mobile web apps?” Polymer is ranked 5th while Tizen is ranked 6th. The most important reason people chose Polymer is:
It provides a base component.
Ranked in these QuestionsQuestion Ranking
Pro Open source
Some parts of the OS are open source.
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.
Con Worst Code Base
Amihai Neiderman, a Kaspersky Labs researcher said, “It may be the worst code I’ve ever seen, Everything you can do wrong there, they do it. You can see that nobody with any understanding of security looked at this code or wrote it.”
Con Lack of apps
Con Aesthetically unappealing
Con Lack of security
With the recent discoveries of a number of security flaws, tizen is no longer a secure OS that it advertises.
Con Based on EFL libraries
A perfect experience of a developer working with EFL: https://what.thedailywtf.com/topic/15001/enlightened
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.