<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PWA on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/pwa/</link><description>Recent content in PWA 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/pwa/index.xml" rel="self" type="application/rss+xml"/><item><title>Performance Budgeting and Optimization</title><link>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/performance-budgeting-optimization/</link><pubDate>Sun, 15 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-system-design-2026-guide/performance-budgeting-optimization/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 8! In our journey through Angular system design, we&amp;rsquo;ve explored how to structure applications, manage state, and build robust routing. But what good is a perfectly designed application if it&amp;rsquo;s slow and unresponsive? This chapter dives deep into &lt;strong&gt;Performance Budgeting and Optimization&lt;/strong&gt;, a critical aspect of delivering high-quality user experiences.&lt;/p&gt;
&lt;p&gt;Performance isn&amp;rsquo;t just a &amp;ldquo;nice-to-have&amp;rdquo;; it&amp;rsquo;s a fundamental requirement. Slow applications lead to frustrated users, higher bounce rates, lower conversion rates, and even poor search engine rankings. As architects, we need to proactively define performance targets, measure against them, and implement strategies to keep our applications fast and fluid.&lt;/p&gt;</description></item><item><title>Chapter 15: Project: Offline-Ready Collaboration Tool</title><link>https://ai-blog.noorshomelab.dev/react-system-design-guide/project-offline-collaboration/</link><pubDate>Sat, 14 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-system-design-guide/project-offline-collaboration/</guid><description>&lt;h2 id="introduction-building-an-uninterrupted-experience"&gt;Introduction: Building an Uninterrupted Experience&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 15! In this exciting project, we&amp;rsquo;re going to roll up our sleeves and build an &amp;ldquo;Offline-Ready Collaboration Tool&amp;rdquo; using React. Imagine a world where your internet connection is flaky, or you&amp;rsquo;re deep in a tunnel, yet your task list or notes app still works perfectly. That&amp;rsquo;s the magic of offline-first design, and it&amp;rsquo;s a critical skill for modern web developers.&lt;/p&gt;
&lt;p&gt;This chapter will teach you how to architect a React application that remains functional and responsive even when the network is unavailable. We&amp;rsquo;ll dive into the core technologies that make this possible, such as Service Workers for intelligent caching and network interception, and client-side databases like IndexedDB for persistent data storage. You&amp;rsquo;ll learn how to provide an &amp;ldquo;optimistic UI&amp;rdquo; that reacts instantly to user input, and how to queue changes for synchronization when connectivity returns.&lt;/p&gt;</description></item><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>