From magic to toys.
Another dirty hack to the responsive image problem.
What to expect from AppCache and how to deal with it.
How to make an IE-only media-queryless stylesheet.
“Working on the web is like trying to fill in a tax return in the middle of an incredible party.”
“Work with the browser, not against it.”
Animation issues and how to solve them.
The benefits of progressive enhancement.
Making network connectivity optional with the ServiceWorker API.
Removing the tap delay in Chrome 32 for Android.
“If you want to get the most out of caching, use different URLs rather than content negotiation.”
“Having a standard way to simplify async coding like this is fantastic!”
“Chrome is experimenting with hiding parts of the URL. I think this is great for the web.”
“Anyone interesting in the web competing with native apps should be excited by this.”
How the web can catch up with and overtake native.
Web apps that work offline are only a matter of time.
The when, where and how of caching and serving content offline-first.
Kinds of things you can do with a background worker.
Client rendering vs. server rendering vs. ServiceWorker rendering.
Should we stop developing the web for a year?
More than you ever wanted to know.
A quick reference to various use-cases.
Why offline should not be an afterthought in web design.
Chrome brings new methods to caches.
An API to ensure data sends despite current network conditions.
Chrome will move to the faster Edge model for rendering.
How to tweak performance, save bandwidth, reduce server costs.
API proposal to handle large upload/downloads in the background.
How you can deliver seemless updates of web apps to users.
Patterns and anti-patterns to speed up web rendering.
“You’re not a developer unless you’ve built a microprocessor using sand and your fists.”
“It seems the web community has decided that developer experience dwarfs user experience, and I’m not sure what to do about that…”
Let’s try to find it out.
“I just saw a loading spinner that wasn’t quite rotating around the centre so my day’s ruined.”
It’s powerful but there are drawbacks.
Did you already know that there’s more than one viewport?
Why you shouldn’t use third party content you don’t trust.
The impact of an attack, and what can be done about it.
Let’s compare the performance of Formula One websites.
Potential new features and behaviours of service workers.
The exciting new things you can do with request streams.
Are you prepared for that?