The videos from Google I/O 2016 are online and there is some great content there. My favorite so far is this one from Ilya Grigorik on resilient web applications. It does a fantastic job explaining unexpected performance and network failures–way better than I did in my JavaScript Forensics talk.

I really enjoyed the statistics on failed network requests in mobile Chrome; way more common than most people imagine. We really need to plan ahead on what kind of experience we create for our users when networks and devices fail.

Chrome Request Failures

Did you like this?

Todd H. Gardner

CEO TrackJS

Todd is a software engineer, business leader, and developer advocate with 20+ years of experience. He is a co-founder and CEO of TrackJS and Request Metrics,...

What to do Next:

1. Try TrackJS on Your Website

TrackJS gives you the visibility to find and fix your errors before users find them. Get started in 5 minutes tracking errors with all the context you'll need to squash the important bugs in your app.

Get Started

2. Get the Debugger Newsletter

Join The Debugger for amazing JavaScript tips, debugging walkthroughs, news, and product releases for Request Metrics. No more than once a week, probably a lot less.

Join Newsletter

Error Monitoring

Performance Monitoring

Remote Debugging

Technologies

Company

Top Errors

[Video] Fast and Resilient Web Apps

What to do Next:

1. Try TrackJS on Your Website

2. Get the Debugger Newsletter

What to do Next:

1. Try TrackJS on Your Website

2. Get the Debugger Newsletter

Related Articles

Common Errors in Next.js Caching

Debugging: "Failed to construct 'Request': Invalid Argument." in Edge

Error Monitoring on Client- and Server-Side in NextJS 14+