Installable Web Apps, Generated on Request
A new Fabricate project is a Vite React app on Cloudflare Workers with no service worker and no web app manifest. Ask for a PWA and the AI writes them into your project: manifest with icons, a registered service worker, and a caching strategy you describe. It is a prompt, not a default - and this page is specific about which parts are which.
The starter templates ship no service worker and no manifest. Nothing here happens unless you ask for it, so put "make this a PWA" in your prompt.
Ask for it and the AI writes a Web App Manifest with icons, display mode and theme colors, so browsers that support installation can offer it.
Say which pages and requests should survive a dropped connection and the AI writes a service worker with a matching cache strategy and an offline fallback.
This part is genuinely automatic: builds are code-split and minified by Vite and served from Cloudflare's edge, PWA or not.
Actions taken offline can be queued and replayed on reconnect if you ask for it. Support for the underlying browser APIs varies, so test on your target devices.
Web push can be generated, but it is not self-contained: you supply VAPID keys and somewhere to store subscriptions, and delivery depends on the browser and platform.
Name it explicitly in your prompt. Without that you get a normal web app - a good one, but not an installable one.
Be concrete: which screens, which data, and what should happen when a request cannot reach the network. The service worker is written from that description.
Open the deployed URL, switch the network off in devtools, and check that the cached screens load and the fallback appears. Verify it rather than assuming it.
Ask for the subscription flow and permission prompt, then supply your own VAPID keys and a place to store subscriptions before it can send anything.
Deploy and send the link. On browsers that support installation, visitors can add it to their home screen from the browser menu.
This page used to say Fabricate generated PWAs automatically - manifest, service worker, background sync and push, all handled. It does not. Every starter project in the catalog is a plain Vite React application served by Cloudflare Workers, with no service worker, no web app manifest and no PWA build plugin. That matters because a buyer who took the old claim at face value would deploy, install nothing, and find no offline behaviour at all.
What actually happens is simpler and still useful: you ask, and the AI writes the code into your project like any other feature. "Make this installable and keep the last five orders readable offline" produces a manifest and a service worker scoped to that requirement. Because it is generated rather than bundled, it is also yours to read and change.
What is automatic regardless: Vite production builds that are code-split and minified, and Cloudflare edge delivery. Fast first load is not a PWA feature and you get it either way.
What has real caveats: push notifications need VAPID keys and subscription storage that you provide, and installation and background behaviour differ across browsers and platforms. Treat any offline or notification requirement as something to test on your target devices rather than something the page can promise on your behalf.
Build SEO-friendly sites with Fabricate AI. Generated apps ship real title, description, canonical and Open Graph tags, ...
Read moreFabricate builds on Cloudflare D1 by default. It has no Supabase connector - but the AI can write the official supabase-...
Read moreBuild apps with Stripe payments using AI. Subscriptions, one-time payments, checkout flows - all integrated without code...
Read moreBuild apps on Cloudflare Workers with AI. Edge computing, global deployment, instant cold starts - serverless made simpl...
Read moreAI code generation, databases, auth, payments and more.
Read moreDescribe your idea and get a deployed full-stack app in minutes.
Read moreJoin thousands of creators building with AI. No coding required. Start free today.