recentpopularlog in


« earlier   
Going Offline, by Jeremy Keith
Web design is complicated. Web development is complicated. Everything seems to be constantly changing—there’s so much to keep track of. But there’s one thing we can confidently say for sure: websites need an internet connection in order to work. Right? Well, even that is no longer true. Thanks to the powerful technology of service workers, you can now design and develop websites that work offline. This is a game-changer! And now you’ve got something new you need to learn. But don’t worry - Jeremy is here to talk you through a whole range of offline strategies. By the end of this presentation, you’ll have all the knowledge and code you’ll need to free your website from the tyranny of the network connection.
fridayfrontend  video  javascript  offline  pwa  serviceworkers 
8 weeks ago by spaceninja
Timing out
In some ways, the offline experience is relatively easy to handle. It’s a binary situation; either you’re online or you’re offline. What’s more challenging—and probably more common—is the situation that Jake calls Lie-Fi. That’s when technically you’ve got a network connection …but it’s a shitty connection, like one bar of mobile signal. In that situation, because there’s technically a connection, the user gets a slow frustrating experience. Whatever code you’ve got in your service worker for handling offline situations will never get triggered. When you’re handling fetch events inside a service worker, there’s no automatic time-out. But you can make one.
fridayfrontend  pwa  offline  timeout  serviceworkers  javascript  performance 
may 2019 by spaceninja
Service Workies
Learn Service Workers inside and out with the new PWA Mastery Game
pwa  games  serviceworkers 
april 2019 by spaceninja
Write Your First Service Worker in 5 Minutes
Write Your First Service Worker in 5 Minutes What is a service worker? A service worker is a little file that will allow you to cache files and other assets on a user's machine. How is this different from server-side caching? Because the assets are stored on a user's machine, rather than a server, there is no need to go across a network. via Pocket
ifttt  pocket  javascript  programming  serviceworkers  tutorial 
april 2019 by jeremyday
Offline fallback page with service worker
A very simple service worker to create an offline fallback page.
fallback  serviceworkers  pwas  scripts  webdev 
april 2019 by angusm
How we built the fastest conference website in the world
The clickbait headline got you here, so let’s make this worth your while! I have no idea whether this is the fastest conference website in the world but I also don’t know that it isn’t; and I’ve spent a completely unreasonable amount of time trying to make it be the fastest conference website in the world. I’m also the creator of AMP, a web component library for making reliably fast websites, and this website is my playground to try out new techniques for future optimizations that I can apply to my day job. Also, fast websites have better conversion rates, which in our case means: sell more tickets.
fridayfrontend  performance  fonts  css  tachyons  atomic  pwa  serviceworkers  animation 
march 2019 by spaceninja
Tuning Performance for New and “Old” Friends
For performance reasons, we often configure our sites to deliver their code in slightly different ways for new and returning visitors. However, for subsequent visits to other pages on our site, many of the resources that pages require will already be in the browser’s cache, so we would not want to inline or push files unnecessarily. Recently, I learned that Service Workers might be a better tool for this job than cookies are.
fridayfrontend  performance  serviceworkers  caching  cookies  javascript 
march 2019 by spaceninja

Copy this bookmark:

to read