Written by the people who maintain the builder, dated, and updated when Chrome, Safari or Google Play change the rules.
Everything between "my site installs from Chrome" and "my app is live on Google Play": PWA readiness, assetlinks.json, the AAB, listing assets, Data safety, closed testing and the review points that catch TWAs specifically.
Read the guide →The three files that turn a website into something people install, what "installed" actually means on Android, iPhone and desktop, and what a PWA cannot do — stated without hype.
Read the guide →Cost, time, capabilities, discovery, updates, monetisation — compared without a thumb on the scale, with the cases where native genuinely wins.
Read the guide →Every field that affects installation and appearance — name, short_name, start_url, scope, display, icons, theme_color, screenshots, shortcuts, id — with what happens when you get each one wrong.
Read the guide →What a service worker intercepts, the four strategies that cover nearly every case, how the builder's three modes map to them, and the rules for never serving the wrong thing from cache.
Read the guide →No install prompt, a share-sheet gesture nobody knows about, push since iOS 16.4, storage rules that favour installed apps — the iOS reality for web apps and the copy that gets people through it.
Read the guide →Exactly when Chrome offers to install, how to trigger the prompt from your own button, what a WebAPK is and why it matters, and how to get the store-like install dialog.
Read the guide →What a TWA is technically, how it differs from a WebView app, Digital Asset Links, the tooling (our builder, Bubblewrap, PWABuilder), Play Billing via the Digital Goods API, and the review considerations.
Read the guide →The Push API and VAPID in plain terms, why iOS requires installation first, permission prompts that get accepted, OneSignal vs rolling your own, and the frequency that keeps subscribers.
Read the guide →A practical taxonomy of your site's files, storage quotas and eviction, versioning without stranding users, and designing an offline page that is actually useful.
Read the guide →From HTTP redirects and 404ing manifests to service workers that cache HTML forever and scopes that dump users into the browser. Each with the symptom, the cause and the fix.
Read the guide →Why the homepage is the wrong place to ask, the one-screen layout that works, platform detection, an install button wired to beforeinstallprompt, iOS instructions, QR entry, and what to measure.
Read the guide →Every decision for one realistic site — a 12-page restaurant site on shared hosting — from choosing the caching mode to the QR code on the tables and the first push notification.
Read the guide →