- Lightest
- Installed PWA
- Store
- Microsoft Store via PWABuilder
- Small native
- Tauri
- Most capable
- Electron
Four routes compared
| Route | Effort | Size | Store listing | Best for |
|---|---|---|---|---|
| Installed PWA | ✓ Lowest | ✓ None | No | SaaS, dashboards, tools |
| PWA in Microsoft Store | Low | ✓ Tiny | ✓ Windows | Reaching Windows users |
| Tauri | Medium (Rust toolchain) | ✓ Small | Optional | Lightweight native features |
| Electron | Medium (Node.js) | Large (100MB+) | Optional | Deep desktop integration |
Installed PWAs
Add a web manifest (name, icons, display: standalone) and a service worker. Chrome and Edge then show an install icon in the address bar; the app opens in its own window, appears in the Start menu or Applications folder, and can be pinned to the taskbar or dock. No build, no store, updates with your site.
Microsoft Store
PWABuilder takes a PWA URL and produces a package for the Microsoft Store, which helps discovery on Windows and gives you reviews and an install button people trust.
Tauri and Electron
Both wrap your web code in a desktop app with native menus, notifications and file access. Tauri uses the operating system's WebView, so apps are small; Electron bundles its own Chromium, so behaviour is identical everywhere but downloads are big. Both need a developer comfortable with a build toolchain.
Where Android fits
Desktop wrappers don't produce Android apps, and Android converters don't produce desktop apps. Many products use a web to app converter for Android and an installed PWA for desktop — one website behind both.
Frequently asked
Can I convert a website to an .exe?
Electron and Tauri produce Windows installers. For simple cases, an installed PWA gives the same windowed experience without an .exe.
Do desktop web apps work offline?
Only if your site caches content with a service worker, or you bundle the files in Electron or Tauri.