Home Start Get started Build an element 1. Get set up 2. Add local DOM 3. Data binding & properties 4. React to input 5. Theming with custom properties Build an app 1. Get set up 2. Create a new page 3. Add some elements 4. Deploy Polymer Feature overview Quick tour Define elements Register an element Declare properties Instance methods Behaviors Local DOM & styling Local DOM Styling Events Handle and fire events Gesture events Data system Data system concepts Work with object and array data Observers and computed properties Data binding Helper elements Tools Tools overview Polymer CLI Document your elements Test your elements Optimize for production Publish an element Advanced tools Services What's new Release notes 1.0 Migration guide About Polymer 1.0 Resources Community Browser compatibility API Reference Polymer.Base array-selector custom-style dom-bind dom-if dom-repeat dom-template Polymer.Templatizer Global settings App Toolbox What's in the box? Using the Toolbox App templates Responsive app layout Routing Localization App storage Service worker Serve your app Case study Shop News Blog Community Home Start Get started Quick tour of Polymer Install Polymer 2.x Build an element 1. Get set up 2. Add local DOM 3. Data binding & properties 4. React to input 5. Theming with custom properties Build an app 1. Get set up 2. Create a new page 3. Add some elements 4. Deploy Polymer Feature overview About this release What's new in 2.0 Upgrade guide Hybrid elements Release notes Custom elements Custom element concepts Define an element Declare properties Shadow DOM & styling Shadow DOM concepts DOM templating Style shadow DOM Custom CSS properties Events Handle and fire events Gesture events Data system Data system concepts Work with object and array data Observers and computed properties Data binding Helper elements Browser support Overview Polyfills ES6 Tools Tools overview Polymer CLI Document your elements Test your elements Web services polymer.json specification Node support Resources Glossary API Reference API Reference Global settings App Toolbox What's in the box? Using the Toolbox App templates Responsive app layout Routing Localization App storage Service worker Deploy Build for production Serve your app The PRPL pattern Case study Shop News Blog Community

We had a great time at Google I/O 2016 last week, where we met hundreds of developers; helped spread the word about Progressive Web Apps; and unveiled the PRPL pattern, the Polymer App Toolbox, and our new-and-improved website.

For those of you who weren’t able to join us in person or online, we’ve compiled a collection of videos you can watch, and you’ll find our original I/O blog post here.

What we mean by #UseThePlatform

One other thing we unveiled at I/O was our new motto-in-hashtag-form, #UseThePlatform, which captures the essential mission of the Polymer Project.

Our project was founded on the premise that—as we complete the transition to a resource-constrained, mobile-first web—we need to lean more heavily on the web platform to give users and developers the experiences they deserve.

In calling you to #UseThePlatform, we’re asking you to join us in rethinking some development patterns we’ve been using for years—patterns that involve working extensively above and around the web platform.

These patterns were born of necessity. When we first started writing web apps the web platform was ill equipped to support us, so we needed to do a lot of heavy lifting ourselves. Our collective efforts have yielded some brilliant ideas and great results.

But building thick layers on top of the platform is inherently costly, and the costs are much harder to bear on mobile, where more users are today. We can reduce these costs if we embrace the modern web platform to its full potential.

To be clear, we don’t think JavaScript is bad, and we don’t think libraries and frameworks are bad either—we’ve been writing them for years. They fill gaps in the platform, and provide useful abstractions for developers. We are all allies in building a better web.

But the web is changing: users are consuming it differently, and the platform now offers us an arsenal of powerful features to help us build apps. We all have to adapt. Frameworks shouldn’t go away, but we think they can and should be leaner.

About the Polymer Project

For more on this topic, we invite you to check out our new About the Polymer Project page, which describes our mission and explains #UseThePlatform in greater depth.