Show HN: Python 3 home automation with Polymer/Material design front end
github.com
github.com
I do think it highlights a problem with using Polymer out of the box though. Like Bootstrap in its early days, Polymer makes it very easy to quickly throw together a fairly polished and professional looking interface. But as more of these come online this style is going to become increasingly stale and generic. And since the design language of Material is so pervasive and rich I think it's going to take a fair amount of work to customize it enough to differentiate an implementation without destroying the integrity of the design. Just tweaking the theme and accent color isn't going to be enough to cure you of looking like a rebranded Google app.
For me at least, the goal is to have a free, usable, recognizable UX. Not to have a "brand". It's open source, it's not supposed to be invested in zero-value branding.
In the past 10-15 years open source software had to catch up with Windows applications, and when they did people would think the problem was in UX. Now that good UX is coming to OSS and we can finally catch up with Apple, you want to reject it?
I agree that in this project it's not important, but marketing (i.e. docs, logo, community, etc) is an integral part of every major open source project out there.
Of course software creators want to have some sort of differentiation between their products and the competitors, but - as a consumer - branding has zero value if the products are interchangeable.
Just looking at Open Source web browsers: look at Chrome/Firefox. If the organizations (Google/Mozilla) behind the development were to start charging in exchange of the use of the brand, wouldn't people drop the branded product and switch to the brandless versions (Chromium/Icefox)?
What would I use it for? What does it replace? What does it make easier?
Components use internally a shadow DOM for representation so that they are untouched by / do not affect the CSS on the main page.