 Good morning. Hey, everyone. I'm Wendy. I'm a product manager on the Polymer project at Google. I'd like to welcome all of you to the third annual Polymer Summit. We're absolutely stoked to be here in Copenhagen for a couple of days celebrating the web platform. It's always awesome to see so many different people at these events, from all over the world, representing all kinds of different companies with all different roles, skills, and passions. And this year is no different. Colts have come from far and wide representing almost 100 different countries. There are people from industry, open source contributors, weekend warriors, and even people who are brand new to web components and Polymer, many of whom we met this morning at the Code Lab. But no matter who you are, where you're from, if you're here in the audience at one of the numerous GDG watch events, or at your own computer on the live stream, we are so glad to have you here. I think I speak for everyone on the Polymer team and on Chrome when I say how much we love these Polymer summits. It's a huge opportunity to get a group of smart, bold, future thinkers in one room to talk about awesome stuff happening in the web platform. We also love being able to meet real developers using our products face to face, to learn more about them and get feedback. Sometimes we don't even find out a company is using Polymer until they reach out at an event like this. If you were at those previous summits or watch the videos on YouTube, you'll look around and notice that they've evolved a bunch over the years. So let's get a show of hands and see where we are. How many of you were with us last year in London? Wow, that's a lot. And what about the first year in Amsterdam? Anyone? Awesome, great. So to all those that have been to past events, welcome back. And to all the new faces, thank you so much for coming out. The first summit was just one day. And frankly, we didn't even really know if people would show up. But luckily they did, over 700 of them. And at that time, Polymer 1.0 had just recently been released and all of the summit talks were from Polymer team members themselves. It was the first big long form opportunity to tell the Polymer story directly to you. What we were doing there, what we were trying to accomplish, and we had such a great time that day that we knew we had to do it again. So the last year in London, we doubled everything. Two full days, more talks, more space, more code labs, more rain, more everything. Polymer 1.0 was in the rearview mirror at that point and now lots of real companies were using Polymer. We wanted to showcase how much our community had grown. So for the first time, we invited some of those companies on stage to tell you how they used Polymer and how important web components and Polymer were to their companies and their workflows. And that brings us to today, to 2017. And things feel a lot different now, even more than they did just last year. You can tangibly feel the web components community coming into its own. So for the first time, we opened up talks to the wider community and we were blown away by all of the suggestions. It took us much longer than anticipated. It took us weeks to go through them all and that, as you know, even delayed registration a little bit. And just from that call for topics, we found out about amazing community projects and several big companies that were using Polymer and a lot of them are here today. We of course couldn't fit everyone, but we did everything we could to give a voice to as many different parts of the community as possible. These are the community speakers you'll see over the next two days. They're from companies large and small, universities and the research world and the open source community. Some will be talking about Polymer, but many will be talking about different web components libraries or different web components tools. We're hitting that fun part of the J-Curve in the web components ecosystem thanks to both those long time web components champions who have done such amazing cutting edge work for so long and the newcomers looking to give a new technology a shot adding your voice to the community. Our first summit was just two years ago next month and it blows my mind when I think about how much things have changed since then. So Polymer project itself has gone through a long journey through many distinct phases to get to where it is today. The Polymer project was conceived a few years ago by some engineers on the Chrome team. They wanted a team of web developers who lives in the future, who can look at web development not as it is today, but as it will be and report back to the present to help inform the platform. The first official phase or the infancy of the project was an experiment to help prove out the idea of web components itself. It was to work side by side with spec authors and browser implementers to find the most natural way to extend the platform, to hand greater power and flexibility over to developers by giving them access to the browser's component model. And they wanted to do this without introducing concepts that would be foreign to the way the web platform itself worked. So we built Polymer primarily as our means to tinker with these new specs, to wrap them together in various ways, to invent new patterns, to anticipate how these specs might be used in the future. And at that point, the only people using Polymer were us, a handful of Google teams, and a little sprinkling of some crazy, brave souls. Oh, also Comcast. Is the Comcast team here? Well, we just clapped it up for them for taking an early risk. So the real promise of web components, though, the real value of baking these new capabilities directly into the platform, it couldn't be realized until the majority of users were on browsers that natively supported web components. So this meant trying to help convince other browser vendors of their value and working with them to ship compatible implementations. We couldn't make this case on our own, though. This required developers to broadly make the case through real-world web component usage and actual, tangible business results. So that was our cue, and we decided to transition the Polymer project from a small experiment to a full-blown production-grade library. And this was to unlock the power of web components in the wild for everyone. So Polymer 1.0 attracted a lot of new friends in a much larger community. Blue-chip companies like General Electric, startups like Simpla, and platforms and web component libraries like Vodin, developers in communities all around the world, from Nigeria to Spain to India and Indonesia, developers everywhere were diving into web components. Unfortunately, our friends over at Safari, Firefox, and Edge, and across-web standard bodies worked hard to hash out a new take on the web components APIs, ones that we could all agree upon, and more importantly, ones that we could all ship. So let's take a look at where we were at around this time last year before V1 of the web component specs. Native web component support was varied and scattered. Template was supported across the board, but other critical features like shadow DOM and custom elements, they were either behind a flag or entirely unsupported. But now, the web component specs have finally gelled with custom elements and shadow DOM V1. The journey wasn't always smooth and it wasn't always as fast as we'd hoped, but we've arrived at our destination. I mean, look at that, it's all green. Yeah, web components are here. They're native on over one billion mobile devices and everywhere else with polyfills. The web reaches farther to more extremes of geography and network conditions than any other technology, and now web components do too. So we were able to transition the Polymer project yet again to its next phase, Polymer 2.0. And Polymer 2.0 paid down some technical debt from the specs upgrading and unlocked that really awesome future forward technology today. A lot of what you're going to hear about at the summit but a lot of that is just capabilities being unlocked with the advancements of 2.0. Major companies from all around the world have continued to adopt web components. Nigeria's e-commerce giants, Kanga and Jumiya Travel, General Electrics, Industrial Internet of Things platform Predix, over 700 projects at Google, India's Olock Cab, as well as a few you'll hear from today, like Netflix, YouTube, Electronic Arts, USA Today, and Simpla. As a community, we've grown WebComponents.org to have over 1,000 high-quality, open-source components in just over six months. I know many of the people who helped us get there are here in the audience, so thank you so much. Because WebComponents.org is huge, it sees over 60,000 monthly active users. It has well over one million page views a month. And over the last six months, we've also seen work on supporting web components happen across the web developer ecosystem, from libraries to frameworks. Major frameworks like Angular and Ember have made public commitments to WebComponents, whether by giving talks on interop or by releasing Glimmer.js with support for WebComponents. Preact has done some amazing work on making it super easy to support WebComponents. And tomorrow, on this stage, Ionic will be here to share how they've been embracing WebComponents as well. So the first goal of the Polymer project was to get WebComponents up the mountain. And well, here we are at the summit. So, what's next? Well, we have this concept of a weirdness budget on the team. It's a very scientific measurement system, but basically it states that we can only be a certain amount of weird. Well, as people, we can be as weird as we want. Like, I could bring my pet lizard Julie into the office and teach him how to use the Polymer CLI and no one bats an eye at that, but as a project, we have a budget. And every project has a weirdness budget because you can only stretch things so far outside the mainstream while still being relatable. And with WebComponents support growing in leaps and bounds, we're finally less weird when it comes to the library itself. You know, super native ES6 classes. But now, we have the opportunity to be less weird on another big front. In this next phase of the project, we can both embrace a lot of the amazing work that's being done in the broader web development ecosystem as the platform grows in capability. We can also expand beyond just a singular view of WebComponents to a much more practical place of building apps that users will love. And all of this is thanks to Polymer 2.0, WebComponents v1, the growing support for other new platform features, and the expansion of our community. With this solid foundation to grow upon, we can more easily take advantage of some major pieces of the web platform and web community. So, I'm extremely excited to announce that as of today, we will be joining the massive, sprawling JavaScript ecosystem of NPM. Woo! And we will be embracing the power of ES modules. This is a critical step in bringing WebComponents to the mainstream. There is so, so much to say on this topic, as you can imagine, and I want all of you to hear it directly from one of the folks working on the projects himself. So, in just a few minutes, Fred Shot from our awesome tools team will share more information on how we're approaching this, why we decided to do it now, and how you can check out a super early sneak preview yourself. And that'll be the first of many awesome talks. Over the next few days, you'll hear about using Polymer with other frameworks, about building Polymer projects with Webpack, using Polymer with Redux, about not using Polymer at all and using other approaches for building WebComponents. You'll hear about how companies, universities, and teams are using WebComponents. You'll learn about how specs even come to be in the first place, not just how to use the platform, but what the platform is. You'll hear from Polymer tech leads on what they've been researching since launching 2.0, about all the collaboration that's happening in the broader WebComponents ecosystem. We'll cover VR, SEO, and server-side rendering for WebComponents. And of course, we'll actually get our hands dirty at the very end with some live coding. So, I'll say it again, we have a packed schedule. We're covering a lot of bases and venturing into territory we've never had the luxury of exploring before. And this summit represents a major transformation for the Polymer project. But as the Polymer project grows, we're always going to be sure to maintain our core values. Of course, to use the platform to take advantage of powerful new features being shipped in the web platform. To minimize abstraction, to keep overhead down while maintaining those developer ergonomics that we all care so much about. And lastly, to inform the platform, to work hand-in-hand with browser vendors to drive changes that push the web platform fundamentally forward. I'm extremely proud of the work we've been doing with Polymer. I'm ecstatic to see how far we've all come together as part of the web components community. And I couldn't be more excited for what's to come next. Thank you.