The app-route element provides a declarative, modular way for web components to interact with the URL. This beta version is complete but may still evolve based on your feedback.

Here's an example of how you can use the app-route (and its included app-location) element:

<app-locationroute="{{route}}"></app-location><app-routeroute="{{route}}"pattern="/tabs/:tabName"data="{{data}}"></app-route><paper-tabsselected="{{data.tabName}}"attr-for-selected="key"><paper-tabkey="foo">Foo</paper-tab><paper-tabkey="bar">Bar</paper-tab><paper-tabkey="baz">Baz!</paper-tab></paper-tabs><neon-animated-pagesselected="{{data.tabName}}"attr-for-selected="key"entry-animation="slide-from-left-animation"exit-animation="slide-right-animation"><neon-animatablekey="foo">Foo Page Here</neon-animatable><neon-animatablekey="bar">Bar Page Goes Here</neon-animatable><neon-animatablekey="baz">Baz Page, the Best One of the Three</neon-animatable></neon-animated-pages>

The app-route element is part of the Polymer project's "app" product-line of components—a set designed to help encapsulate structured patterns for building large, complex applications using web components. Other elements that may fill out this product line—including i18n components—are still in their earlier stages. We'll being opening up these elements in a similar "beta" stage once they're at a point of stability to be able to receive meaningful feedback, and are targeting May to have the next handful of these components released. We'd also love to hear about the common application-level problems you run into when building web component-driven apps, that could form the basis of future app elements—please feel free to file issues on the app-elements meta-repo with ideas.