Progressive Web App Conversion Plan
Turn a web app into an installable, offline-capable PWA.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Help me decide whether and how to convert my web app to a progressive web app. Current app (framework, hosting, features): [CURRENT_APP]. Users and how they use it (offline, mobile, repeat): [USER_BEHAVIOR]. Team skills and time: [TEAM_AND_TIME]. Walk through the tree: 1. Is there a real user need for installability, offline use, push notifications, or faster repeat loads? If not, a good responsive site may be enough. Say so if that is the case. 2. Prerequisites: HTTPS everywhere, a web app manifest (name, icons, start URL, display mode, theme color), and a service worker. 3. Caching strategy per resource type: static assets (cache first with versioning), API data (network first or stale while revalidate), pages (network first with offline fallback). Pick for my app and explain the risks of stale data. 4. Offline behavior: which features work, which show a clear message, and how data entered offline syncs (background sync, conflict handling). 5. Updates: how new versions reach users without breaking them (update prompt). 6. Notifications: only if there is value; permission request timing. 7. Platform differences and limits on iOS and desktop [VERIFY current support]. 8. Testing: Lighthouse checks, offline mode, install flow, and update flow. Output a phased plan with tasks, estimates, and risks, a sample manifest, and a service worker outline in code with comments.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.