40 Matching Annotations
  1. Jan 2021
    1. v1 tabs tightly couple to their v1 Cache; v2 tabs tightly couple to their v2 Cache. This tight coupling makes them “application caches.” The app must be completely shut down (all tabs closed) in order to upgrade atomically to the newest cache of code.
  2. Nov 2020
    1. We won’t go into all the details that make an application a PWA, because it all sort of depends on who you ask.
    1. They are rapid to develop, cross-platform and responsive by nature. JavaScript provides a lot of frameworks (such as Vue, React) and dedicated front-end component libraries to boost productivity (Bootstrap, Material UI). You write your code once and deploy you application on every platform;
    2. These apps combine the best of web and native solutions:
    3. Progressive Web Apps can be installed on most devices like native apps. They are meant to be reliable (work on each platform, even offline), fast and provide a native-like user experience.
    4. For example, your application should work offline, but it doesn’t mean that you must set-up a background queue or store your data in a persistent storage – a offline message (e.g. “You’re offline, check your network status.”) is enough.
    1. Can you image your favorite web app working offline? Well, Progressive Web Apps (PWA) are here. One of their main benefits is that Service Workers will allow you to continue loading your apps even when there’s no internet connection.
    2. Service Workers are also helpful for offline caching and performance. You can write code to cache your application shell to work offline and populate its content using JavaScript.
  3. Oct 2018
    1. A completely different Service Workers’ storyThis section was added on Feb, 8th.Apple followed the Service Worker API, but it creates an entirely different story of what it is and what we can do with it in the future. The main differences appear when Apple says:“To keep only the stored information that is useful to the user, WebKit will remove unused service worker registrations after a period of a few weeks. Caches that do not get opened after a few weeks will also be removed. Web Applications must be resilient to any individual cache, cache entry or service worker being removed.”https://webkit.org/blog/8090/workers-at-your-service/That is a huge change! At Chrome, Firefox, Samsung Internet, and other browsers, a Service Worker registration is not going to be unregistered automatically, and we can rely on being there in the future. That’s why an installed PWA will be able to work offline in the future. But with Apple’s idea of a service worker, there is no guarantee that the service worker or the cache will be available in the future. It might be if the user comes back to the web app within “a few weeks.” I know, the web app should work anyway while online, but we can’t guarantee one of the key concepts of PWAs: offline access.
  4. Sep 2018