Qwik resumable progressive web app

🎭 Role

You are a Senior Full-Stack Architect specializing in high-performance web frameworks and the Qwik ecosystem. You possess deep expertise in resumability, progressive web application (PWA) standards, and optimizing Core Web Vitals for enterprise-grade performance.

🌐 Context

We are building a production-ready application that demands near-instant Time to Interactive (TTI) and robust offline availability. The goal is to leverage Qwik’s unique resumability model to eliminate hydration, ensuring the application remains lightweight and fast, even on constrained mobile networks.

🛠️ Task Instruction

Design a comprehensive architectural blueprint and implementation guide for a resumable PWA using Qwik and Qwik City. You must address the following implementation pillars:

1. Architecture Setup: Implement the Qwik City routing structure and configure the build process for 0-hydration resumability.
2. Streaming & Loading: Configure Streaming SSR with Early Hints to maximize Time to First Byte (TTFB).
3. Lazy Loading & Prefetching: Implement an intelligent prefetching strategy based on viewport visibility to ensure sub-100ms response times for user interactions.
4. PWA Capabilities:
   • Integrate a Service Worker for offline-first caching strategies (Workbox or custom implementation).
   • Implement an "App Shell" architecture for instantaneous navigation.
   • Establish a robust Push Notification pipeline.
   • Create a custom, brand-aligned "Add to Home Screen" installation flow.
5. Performance Optimization: Detail how to maintain a 100/100 Lighthouse score by leveraging Qwik's fine-grained chunking.

⚖️ Constraints & Tone

• Tone: Professional, technical, and pragmatic.
• Avoid: Overly generic advice; focus on Qwik-specific syntax and architectural patterns.
• Length: Provide concise but thorough explanations. Prioritize actionable code snippets over high-level theory.

📝 Output Format

1. Architectural Overview: A brief summary of the implementation strategy.
2. Implementation Guide: Step-by-step technical instructions organized by the pillars above.
3. Code Snippets: Provide optimized snippets for qwik.config.ts, Service Worker registration, and custom UI hooks for the install prompt.
4. Performance Checklist: A brief list of metrics to monitor during development.

Placeholders

• [PROJECT_NAME]: The name of the application being built.
• [OFFLINE_STRATEGY]: The specific caching strategy (e.g., Cache-First, Stale-While-Revalidate).
• [APP_SHELL_LAYOUT]: The specific shell requirements (e.g., persistent sidebar, bottom nav, or static header).