<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service Worker on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/service-worker/</link><description>Recent content in Service Worker on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 15 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/service-worker/index.xml" rel="self" type="application/rss+xml"/><item><title>Project: Creating an Offline-Capable Field App</title><link>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/project-offline-field-app/</link><pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/project-offline-field-app/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 16! In the world of modern web applications, the expectation for seamless user experience often extends beyond a stable internet connection. Imagine a field technician inspecting equipment in a remote area, a delivery driver making notes in a dead zone, or a medical professional accessing patient records on the go. For these scenarios, an application that simply stops working when offline is not just inconvenient—it&amp;rsquo;s a critical failure.&lt;/p&gt;</description></item></channel></rss>