Signaling Polymer's production readiness, Google announced release 1.0 at its annual I/O developer conference. A core library used to build and style Web components, Polymer transitioned rapidly from concept to production release in less than two years.
The Web's explosive growth and competition between browser makers drove Web standards bodies such as W3C to ignore a component-based service-oriented architecture (SOA) model. Polymer aims to reverse this trend by allowing Web developers to build functional and design elements that fit a familiar SOA-like architecture in which components called elements provide services to other components through clearly defined interfaces.
Standards and the extensible Web manifesto
Polymer includes libraries used to create custom elements, as well as a catalog of elements built by the Polymer engineering team for adding functionality to Web page such as credit card entry fields, check boxes, animations and transitions. The Polymer open source community that includes Google and non-Google developers anticipates an ecosystem around Polymer that will create and license a large independent catalog of custom elements.
Building bridges between developers and designers
Polymer extends beyond efficiency in Web development to the design and branding of websites. Using Google's Material Design language as the reference for creating themes and branding at an elemental level, Polymer aims to distribute a consistent theme and user experience (UX) across a Web property from within the Polymer elements. That Google intends for Polymer to scale across large, complex websites with large repositories of elements is clear.
Polymer also promises also to tame the naturally contentious relationship between designers concerned with Web page UX and developers concerned with Web page functionality. Developers will be able to use prebuilt Polymer elements that include designs and themes, thereby eliminating the need to modify complex Web page source code to match designers' specifications, and potentially introducing hard-to-find and harder-to-fix bugs.
Sign up for Computerworld eNewsletters.