Browser Engines & PWAs
Studies in this cluster, in series order. Each one keeps its own URL.
Frontend
Browser and PWA internals: service workers, the rendering pipeline, and the multi-process model you can defend in interviews.
Browser Engines & PWAs
6 studies- 1.Browser Engines & PWAs — Service Workers, Rendering & Process ModelInterview map of browser architecture and the PWA platform: process model, rendering, Service Workers, and when a PWA beats a native shell.
- 2.Service Workers — Lifecycle, Install/Activate, Fetch & ClientsA Service Worker is an origin-scoped network proxy. Register, install, activate, skipWaiting, clients.claim, fetch, and scope explain real update bugs.
- 3.PWA Cache Strategies — Cache-First, Network-First, SWR & Workbox PatternsPick cache-first, network-first, or stale-while-revalidate per resource class. Workbox encodes the patterns. You still own versioning and update UX.
- 4.Web App Manifest, Installability, Push/Background Sync & Offline UXThe manifest names the installed app. Installability is HTTPS, a worker, icons, and engagement. App shell, push, and background sync still have platform gaps, especially on iOS.
- 5.Browser Rendering Pipeline — DOM, CSSOM, Layout, Paint, Composite & CRPBytes become pixels through DOM, CSSOM, render tree, layout, paint, and composite. The critical rendering path is what blocks first paint. Thrashing and layers explain jank.
- 6.Browser Process Model — Site Isolation, Blink, Network Stack & V8 PipelineChromium splits browser, renderer, GPU, network, and utility processes. Site isolation, Blink, and the V8 Ignition-to-TurboFan path are the systems interview, not a JS language lecture.