project_path: /web/_project.yaml book_path: /web/shows/_book.yaml

{# wf_updated_on: 2015-11-17 #} {# wf_published_on: 2015-11-17 #} {# wf_youtube_id: iIV1xPFXmBs #}

RAIL in the real world (Chrome Dev Summit 2015) {: .page-title }

<div class="video-wrapper"> <iframe class="devsite-embedded-youtube-video" data-video-id="iIV1xPFXmBs" data-autohide="1" data-showinfo="0" frameborder="0" allowfullscreen> </iframe> </div>

RAIL is the Chrome team’s way of thinking about performance, but how can you apply it to your projects? Does it work as-is, or do you need to do tweak things first? Let’s take a look at what RAIL involves when the rubber hits the road.

Paul Lewis is a Developer Advocate at Google. He spends his time trying to figure out patterns for making the next generation of web apps beautiful, integrated, useful, and performant. He tries lots of things in the process, which is why he looks like a crash test dummy.

Watch more talks from Chrome Dev Summit 2015: https://goo.gl/e4c7vD

Subscribe to the Chrome Developers channel at: https://goo.gl/OUF4e2