-
@windowsdev I’ve been working on the web for over 20 years and have spent the bulk of that time focused on helping the web reach more people. As such, I’ve been a major proponent of the progressive enhancement philosophy and accessibility.Permalink On twitter.com
AaronGustafson
Mood +5 🙂
-
@windowsdev I’ve consulted, presented, and written on these topics for quite some time now. If you’re interested, here are some links: noti.st/aarongustafson aaron-gustafson.com/publications aaron-gustafson.com/appearancesPermalink On twitter.com
-
@windowsdev When I first heard about ServiceWorker, I approached it as I approach most new JavaScript APIs: with a healthy dose of skepticism. The underlying idea—control network requests to reduce network dependency—is really interesting.Permalink On twitter.com
-
@windowsdev However, ServiceWorker is still dependent on JavaScript running as expected (which doesn’t always happen) to get any of the benefits. Digging in further, however, I was impressed with how it was designed as a progressive enhancement.On twitter.com
-
@windowsdev If your users don’t have ServiceWorker support, they get the same experience we’ve offered them for the last 25 years. But (!) if they use a browser that supports ServiceWorker, the whole site gets a lot faster.Permalink On twitter.com
-
@windowsdev ServiceWorker is one of the three core components of a progressive web app (PWA). The other two are the Web App Manifest (a collection of information about your site) and HTTPS for security. These features make every site better.Permalink On twitter.com
-
@windowsdev I recognized the PWAs were the start of something really big because they presented the first real opportunity for the web to assert itself beyond the browser.Permalink On twitter.com
-
@windowsdev So many "apps" today are built on the web, but don’t speak its language. Now we can actually build these apps using the web from start to finish. And, being a huge fan of the web, I’m excited by that.Permalink On twitter.com