<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Libin V Babu on Medium]]></title>
        <description><![CDATA[Stories by Libin V Babu on Medium]]></description>
        <link>https://medium.com/@libinvbabu?source=rss-364ea438aab4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GoZj15Quxhw4X6nxxvi49Q.jpeg</url>
            <title>Stories by Libin V Babu on Medium</title>
            <link>https://medium.com/@libinvbabu?source=rss-364ea438aab4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:54:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@libinvbabu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Advanced Caching Strategies with Workbox: Beyond StaleWhileRevalidate]]></title>
            <link>https://medium.com/animall-engineering/advanced-caching-strategies-with-workbox-beyond-stalewhilerevalidate-d000f1d27d0a?source=rss-364ea438aab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d000f1d27d0a</guid>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Libin V Babu]]></dc:creator>
            <pubDate>Thu, 24 Oct 2024 07:01:34 GMT</pubDate>
            <atom:updated>2024-10-24T07:01:34.000Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Three years ago, we implemented <a href="https://medium.com/animall-engineering/best-caching-strategies-progressive-web-app-pwa-c610d65b2009">caching strategies</a> in our Progressive Web App (PWA) at <strong>Animall</strong> using Workbox. Today, I’m excited to share an evolution of our approach that offers more control and efficiency. Whether you’re facing challenges with asset freshness or simply looking to optimize your PWA’s performance, this post will introduce you to a powerful custom caching strategy that complements Workbox’s built-in options.</p><h3>The Problem with Standard Strategies</h3><p>Workbox offers several caching strategies, including:</p><ol><li><strong>CacheFirst</strong>: Great for assets that don’t change often, but can serve stale content.</li><li><strong>NetworkFirst</strong>: Ensures fresh content but can be slow on poor connections.</li><li><strong>StaleWhileRevalidate</strong>: A balance between the two, but still makes unnecessary network requests.</li></ol><p>Let’s focus on StaleWhileRevalidate, a popular choice for many developers. Here&#39;s how it works:</p><ol><li>Returns a response from the cache (if available) immediately.</li><li>Sends a network request and updates the cache in the background.</li></ol><pre>import { StaleWhileRevalidate } from &#39;workbox-strategies&#39;;<br><br>workbox.routing.registerRoute(<br>  ({request}) =&gt; request.destination === &#39;script&#39;,<br>  new StaleWhileRevalidate()<br>);</pre><p>While this strategy is often effective, it has a key drawback: it always makes a network request, even if the asset hasn’t changed. This can lead to unnecessary data usage and potential performance issues.</p><h3>Introducing handleVersionedCache</h3><p>Our custom handleVersionedCache strategy addresses this issue by implementing version-based caching. Here&#39;s how it works:</p><ol><li>Checks the requested URL for a version parameter.</li><li>If the cached version matches the requested version, serves from cache without a network request.</li><li>If versions don’t match or the asset isn’t cached, fetches from the network and updates the cache. This deletes the old cached file as well from the cache if exists.</li></ol><p>Let’s dive into the implementation:</p><pre>async function handleVersionedCache(request, cacheName) {<br>  const cache = await caches.open(cacheName);<br>  const url = new URL(request.url);<br>  const baseUrl = url.origin + url.pathname;<br>  const newVersion = url.searchParams.get(&#39;v&#39;);<br>  const existingResponse = await cache.match(request);<br>  <br>  if (existingResponse) {<br>    const existingUrl = new URL(existingResponse.url);<br>    const existingVersion = existingUrl.searchParams.get(&#39;v&#39;);<br>    <br>    // Return cached version if it matches the requested version<br>    if (newVersion === existingVersion) {<br>      return existingResponse;<br>    }<br>  }<br>  <br>  // Update cache if version has changed<br>  const keys = await cache.keys();<br>  for (const key of keys) {<br>    const keyUrl = new URL(key.url);<br>    if (keyUrl.origin + keyUrl.pathname === baseUrl) {<br>      await cache.delete(key);<br>    }<br>  }<br>  <br>  try {<br>    const response = await fetch(request);<br>    if (response &amp;&amp; response.ok) {<br>      await cache.put(request, response.clone());<br>    }<br>    return response;<br>  } catch (error) {<br>    // If fetch fails, return the existing response if available, otherwise return the error<br>    return existingResponse || Response.error();<br>  }<br>}</pre><p>To use this strategy in your service worker, you can register it like this:</p><pre>workbox.routing.registerRoute(<br>  ({request}) =&gt; <br>    [&#39;style&#39;, &#39;script&#39;, &#39;worker&#39;].includes(request.destination),<br>  async ({request}) =&gt; {<br>    return handleVersionedCache(request, &#39;assets-cache&#39;);<br>  }<br>);</pre><h3>How to Use in Your Application</h3><p>To take advantage of this strategy, add a version parameter to your asset URLs:</p><pre>&lt;script src=&quot;/js/main.js?v=1.0.0&quot;&gt;&lt;/script&gt;<br>&lt;link rel=&quot;stylesheet&quot; href=&quot;/css/styles.css?v=2.3.4&quot;&gt;</pre><p>When you update an asset, simply change its version:</p><pre>&lt;script src=&quot;/js/main.js?v=1.0.1&quot;&gt;&lt;/script&gt;</pre><h3>Benefits of handleVersionedCache</h3><ol><li><strong>Version-based updates</strong>: Assets are updated based on their version, not just their URL.</li><li><strong>Efficient caching</strong>: Serves from cache when versions match, reducing unnecessary network requests.</li><li><strong>Automatic cache cleanup</strong>: Old versions of assets are removed from the cache.</li><li><strong>Fallback to network</strong>: If cached content isn’t available, it fetches from the network.</li></ol><h3>Comparison with Other Strategies</h3><p>Let’s compare handleVersionedCache with Workbox’s built-in strategies:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B0qYutJAtC2dGctwgtqZOQ.png" /></figure><ul><li><strong>StaleWhileRevalidate</strong>: Serves cached content quickly while updating in the background.<br><strong>Difference</strong>: handleVersionedCache only updates when versions change, reducing network usage.</li><li><strong>CacheFirst</strong>: Prioritizes cached content for speed.<br><strong>Difference</strong>: handleVersionedCache ensures you&#39;re not serving outdated content by checking versions.</li><li><strong>NetworkFirst</strong>: Ensures fresh content from the network but might cause delays if network is slow.<br><strong>Difference</strong>: handleVersionedCache is faster as it serves from cache unless the version changes.</li></ul><h3>Similar Strategies in the Ecosystem</h3><p>While our handleVersionedCache strategy offers a unique approach to version-based caching, it&#39;s worth exploring similar strategies that exist in the web development ecosystem. Understanding these can provide context and help you make informed decisions about your caching approach.</p><h3>1. Workbox: CacheableResponsePlugin</h3><p>Workbox doesn’t have a built-in versioning strategy, but it does offer the CacheableResponsePlugin which can be used to cache responses based on headers. This can be utilized for a form of versioning, though it&#39;s not as fine-grained as our handleVersionedCache.</p><pre>import { CacheFirst, CacheableResponsePlugin } from &#39;workbox-strategies&#39;;<br><br>new CacheFirst({<br>  plugins: [<br>    new CacheableResponsePlugin({<br>      statuses: [0, 200],<br>      headers: {<br>        &#39;X-Is-Cacheable&#39;: &#39;true&#39;,<br>      },<br>    }),<br>  ],<br>});</pre><p>This approach requires you to set custom headers on your server responses, which might not always be feasible.</p><h3>2. sw-precache (deprecated)</h3><p>Google’s now-deprecated sw-precache library had a concept of file revisions. It would generate a service worker that included a mapping of URLs to hashes of the file contents:</p><pre>{<br>  &quot;/styles/main.css&quot;: &quot;hash1&quot;,<br>  &quot;/scripts/main.js&quot;: &quot;hash2&quot;<br>}</pre><p>This approach required a build step to generate the service worker, which differs from our runtime approach.</p><h3>3. Webpack’s cache-loader</h3><p>While not a service worker strategy, Webpack’s cache-loader uses a similar concept for build-time caching:</p><pre>module.exports = {<br>  module: {<br>    rules: [<br>      {<br>        test: /\.js$/,<br>        use: [<br>          &#39;cache-loader&#39;,<br>          &#39;babel-loader&#39;<br>        ],<br>      },<br>    ],<br>  },<br>};</pre><p>It uses the hash of the file contents to determine if a cached version can be used, similar to our version parameter.</p><h3>4. Custom Implementations</h3><p>Many developers have created custom versioning strategies similar to handleVersionedCache. For example, the Mozilla Developer Network (MDN) documentation includes an example of a &quot;versioned cache&quot; in their service worker cookbook:</p><pre>self.addEventListener(&#39;fetch&#39;, function(event) {<br>  event.respondWith(<br>    caches.open(&#39;mysite-dynamic&#39;).then(function(cache) {<br>      return cache.match(event.request).then(function(response) {<br>        var fetchPromise = fetch(event.request).then(function(networkResponse) {<br>          cache.put(event.request, networkResponse.clone());<br>          return networkResponse;<br>        })<br>        return response || fetchPromise;<br>      })<br>    })<br>  );<br>});</pre><p>This example doesn’t use explicit versioning but demonstrates the concept of updating cache entries.</p><h3>Comparison with handleVersionedCache</h3><p>Our handleVersionedCache strategy differs from these approaches in several ways:</p><ol><li><strong>Fine-grained control</strong>: Unlike Workbox’s CacheableResponsePlugin, we can version individual assets without relying on server-set headers.</li><li><strong>Runtime versioning</strong>: Unlike sw-precache, our strategy doesn’t require a build step to generate version information.</li><li><strong>Specific to service workers</strong>: Unlike Webpack’s cache-loader, our strategy is designed specifically for browser caching via service workers.</li><li><strong>Explicit versioning</strong>: Unlike many custom implementations, we use an explicit version parameter, making it easier to manage and update versions.</li></ol><h3>Browser Compatibility</h3><p>We use Babel to transpile our service worker code, ensuring compatibility with older browsers while allowing us to use modern JavaScript features. This approach allows us to leverage advanced caching strategies without sacrificing browser support.</p><h3>Conclusion</h3><p>The handleVersionedCache strategy offers a powerful complement to Workbox’s built-in options. By integrating this approach, we’ve significantly improved caching efficiency at <strong>Animall</strong>. This strategy provides fine-grained control over asset caching and updates, crucial for fast-evolving web applications. With proper caching strategies, your PWA can be both performant and resource-efficient. Keep experimenting with custom solutions when needed to meet your specific needs.</p><p>Happy coding, and may your PWAs be ever performant!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d000f1d27d0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animall-engineering/advanced-caching-strategies-with-workbox-beyond-stalewhilerevalidate-d000f1d27d0a">Advanced Caching Strategies with Workbox: Beyond StaleWhileRevalidate</a> was originally published in <a href="https://medium.com/animall-engineering">Animall Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Caching strategies — Progressive Web App (PWA)]]></title>
            <link>https://medium.com/animall-engineering/best-caching-strategies-progressive-web-app-pwa-c610d65b2009?source=rss-364ea438aab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c610d65b2009</guid>
            <category><![CDATA[service-worker]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[workbox]]></category>
            <dc:creator><![CDATA[Libin V Babu]]></dc:creator>
            <pubDate>Tue, 19 Jan 2021 16:28:58 GMT</pubDate>
            <atom:updated>2021-01-19T16:28:58.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>Best Caching strategies — Progressive Web App (PWA)</h3><p>The main challenge I’ve faced while building a web app was the page loading speed. The best way to speed up a page is to load the assets from the cache and thus avoid network calls. This is really important when your users are on a slow network. This time I’ve decided to jump on to service workers and make full use of its caching strategies.</p><p>Popular caching strategies are:</p><ol><li>Cache first, Network fallback.</li><li>The network first, Cache fallback.</li><li>Stale while revalidate</li><li>Network only</li><li>Cache only</li></ol><p>I’ll briefly explain what these strategies are and where we can apply these.</p><h3>Cache first, Network fallback.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1004/0*m5KMbLba3VuXQHEq.png" /></figure><p>The service worker will loads the local (cached) assets (HTML, CSS, images, fonts, etc.), if possible, bypassing the network. If cached content is not available, the service worker returns a response from the web instead and caches the network response. This strategy can be used when dealing with remote resources that are very unlikely to change, such as static images.</p><h3>The network first, Cache fallback.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*tEZqxxI09JcqJ7lW.png" /></figure><p>In this strategy, the service worker will check the network first for a response and, if successful, returns current data to the page. If the network request fails, then the service worker returns the cached entry instead. Use this when data must be as fresh as possible, such as a real-time API response, but you still want to display something as a fallback when the network is unavailable.</p><h3>Stale while revalidate</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*oildRObl4R4mXtoH.png" /></figure><p>The stale-while-revalidate pattern allows you to respond to the request as quickly as possible with a cached response if available, falling back to the network request if it’s not cached. The network request is then used to update the cache. This is a fairly common strategy where having the most up-to-date resource is not vital to the application.</p><h3>Network only</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*Va2ch-FoXbz90mC4.png" /></figure><p>In this, the service worker will only check the network. There is no going to the cache for data. If the network fails, then the request fails. This can be used when only fresh data can be displayed on your site.</p><h3>Cache only</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1013/0*pFecqTHn4K5JDoLi.png" /></figure><p>The data is cached during the install event so that you can depend on the information being there. This can be useful if you have your own precaching step.</p><p>While you can implement these strategies yourself manually, using <a href="https://developers.google.com/web/tools/workbox">workBox</a> is recommended for service worker caching. Workbox is a set of libraries that can power a production-ready <a href="https://web.dev/service-workers-cache-storage/">service worker</a> for your <a href="https://web.dev/progressive-web-apps/">Progressive Web App</a>.</p><p>The approach I’ve taken at Animall are:<br>1. <strong>Pre-cache</strong> the home page assets when the user lands on the onboarding page through the install event. With this, once the user completes the onboarding, all the static assets needed to load the home page are already available in the cache.</p><pre>self.addEventListener(‘install’, async function (event) {<br>  event.waitUntil(caches.open(‘assets’).then(function (cache) {<br>    return cache.addAll(filesToCache);<br> }));<br>});</pre><p><em>filesToCache </em>in the above code is an array of files to be cached at the install event.</p><p>2.<strong> Network-only </strong>strategy to handle all navigations.</p><pre>var networkOnly = new NetworkOnly();<br>var navigationHandler = async function navigationHandler(params) {<br>  try {<br>    return await networkOnly.handle(params);<br>  } catch (error) {<br>    return caches.match(FALLBACK_HTML_URL, {<br>      cacheName: &#39;offline&#39;<br>    });<br>  }<br>};</pre><pre>// Register this strategy to handle all navigations.<br>var navigationRoute = new workbox.routing.NavigationRoute(navigationHandler);<br>registerRoute(navigationRoute);</pre><p>This ensures that the pages are loaded from the network only and fall back to an offline page if the internet is not available.</p><p>3. <strong>Stale While Revalidate </strong>strategy for CSS and js assets</p><pre>registerRoute(function(_ref2) {<br>    var request = _ref2.request;<br>    return request.destination === &#39;style&#39; || request.destination === &#39;script&#39;;<br>}, new StaleWhileRevalidate({<br>    cacheName: &#39;assets&#39;,<br>    plugins: [new CacheableResponsePlugin({<br>        statuses: [200]<br>    })]<br>}));</pre><p>All the CSS/js assets are loaded from the cache and returns to the user immediately. Same time, it will check for any updates also from the network as well. If the file is updated in the network, the service worker will update the cache. So next time, when the user loads the same page, he will get the updated version.</p><p>4. <strong>Cache First </strong>for the images</p><pre>registerRoute(function(_ref) {<br>    var request = _ref.request;<br>    return request.destination === &#39;image&#39;;<br>}, new CacheFirst({<br>    cacheName: &#39;images&#39;,<br>    plugins: [new CacheableResponsePlugin({<br>        statuses: [200]<br>    }), new ExpirationPlugin({<br>        maxEntries: 50,<br>        maxAgeSeconds: 60 * 60 * 24 * 30, // 30 Days<br>        purgeOnQuotaError: true<br>    })]<br>}));</pre><p>The images we use are usually not updated on the server frequently. So I’ve used the cache first strategy for loading the static images with few options as well.<em> </em>Since the images can bloat your cache disk quickly, we have put a maximum image limit in the cache with <em>maxEntries</em>. Use <em>purgeOnQuotaError </em>along with this to make sure that the cache is cleared when the quota exceeds. Also, I’ve applied <em>maxAgeSeconds </em>to expire the image cache.</p><p>If you are excited about solving similar problems, <a href="https://animall.in/pashu-suvidhaen">Animall</a> is looking for people like you to build the next billion users&#39; platform. Animall is a top tier VC funded startup building an online platform to empower millions of dairy farmers, ushering in the next digital white revolution! You can find the opportunities <a href="https://angel.co/company/animall-1">here</a> or shoot an email to <a href="/service/mailto:mission@animall.in">mission@animall.in</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c610d65b2009" width="1" height="1" alt=""><hr><p><a href="https://medium.com/animall-engineering/best-caching-strategies-progressive-web-app-pwa-c610d65b2009">Best Caching strategies — Progressive Web App (PWA)</a> was originally published in <a href="https://medium.com/animall-engineering">Animall Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Install the Pratilipi Progressive Web App(PWA) natively on macOS]]></title>
            <link>https://tales.pratilipi.com/install-the-pratilipi-progressive-web-app-pwa-natively-on-macos-6ba75d46d0e0?source=rss-364ea438aab4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ba75d46d0e0</guid>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[pratilipi]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[google-chrome]]></category>
            <dc:creator><![CDATA[Libin V Babu]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 13:25:44 GMT</pubDate>
            <atom:updated>2019-08-08T13:25:44.844Z</atom:updated>
            <content:encoded><![CDATA[<p>Chrome 73 (released on March 12, 2019) added the support for installing Progressive Web Apps(PWA) on your macOS. But on desktop, there’s no indication to a user that the PWA is available for a website or not. The install button is hidden inside the three-dot menu.</p><p>In Chrome 76 (released on July 30, 2019), an install button (+ icon) is added to the address bar if the PWA is available. By clicking this icon, the Install prompt will open.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vld6EO_Uevsv1ajDQl3vag.jpeg" /><figcaption>Install PWA on macOS through Google Chrome 76</figcaption></figure><h3>Why should you use a PWA?</h3><blockquote>Desktop progressive web apps can be ‘installed’ on the user’s device much like native apps. They’re <strong>fast</strong>. Feel <strong>integrated </strong>because they launched in the same way as other apps, and run in an app window, without an address bar or tabs. They’re <strong>reliable</strong> because service workers can cache all of the assets they need to run. And they create an <strong>engaging</strong> experience for users.</blockquote><h3>Does Pratilipi provide a PWA?</h3><p>The good news is, Pratilipi meets all the Progressive Web App installability criteria and Google Chrome will show an install button in the Omnibox indicating to the user that the PWA can be installed. You can go to any of the available 10 languages from <a href="https://www.pratilipi.com/">pratilipi.com</a> and click the install icon to use the native Pratilipi App on macOS. Check the below video.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FEiXtKTjcLRE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DEiXtKTjcLRE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FEiXtKTjcLRE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/74cf932a808b344b3cb5464b3f245670/href">https://medium.com/media/74cf932a808b344b3cb5464b3f245670/href</a></iframe><h4>How to access Pratilipi App</h4><p>Once installed, the Pratilipi App will be accessible through spotlight search, launchpad, etc just like any other native apps. Because it is a Chrome App, it can be accessed through <strong><em>chrome://apps/ </em></strong>as well. It also has its icon in the system dock as well as below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-kjtewww6xrurgGWeQWNQ.jpeg" /><figcaption>Pratilipi Icon on the system dock</figcaption></figure><h4>How to uninstall a PWA</h4><p>To uninstall a PWA, just open the App and click on the three-dot menu from the top right. Then click the Uninstall option. That’s it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gR5ZCvbk6dWQVFznmMRQA.jpeg" /><figcaption>Uninstall PWA</figcaption></figure><p><strong>Note</strong>: Pratilipi PWA is also available on Windows Desktop, Linux, Android and iOS as well through Google chrome. If you have an Android Phone, try our <a href="https://play.google.com/store/apps/details?id=com.pratilipi.mobile.android&amp;referrer=utm_source=medium&amp;utm_medium=medium&amp;utm_campaign=app_download">native App</a> as well.</p><p>For more information regarding PWA, please refer to <a href="https://developers.google.com/web/progressive-web-apps/desktop">https://developers.google.com/web/progressive-web-apps/desktop</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ba75d46d0e0" width="1" height="1" alt=""><hr><p><a href="https://tales.pratilipi.com/install-the-pratilipi-progressive-web-app-pwa-natively-on-macos-6ba75d46d0e0">Install the Pratilipi Progressive Web App(PWA) natively on macOS</a> was originally published in <a href="https://tales.pratilipi.com/">Team Pratilipi</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>