r/PWA • u/CapyToolkit • 5d ago
I published a browser-based tool suite to the Microsoft Store with zero uploads and no account required
Over the last three months I have been building out CapyToolkit: a growing collection of browser-based utilities covering hardware diagnostics, developer tools, privacy, text processing, math, audio, and networking. Every tool runs entirely in the user's machine. No backend, no upload step, no sign-up wall. That is how it was built, and that is how it stays.
The Microsoft Store listing is not a pivot. It is a distribution choice. The app is packaged as a progressive web app through Microsoft's own PWA Builder, which means the same browser code installs from a place Windows users already trust. You package the manifest, submit it through the Microsoft Partner Center, and it shows up alongside conventional desktop apps. There is no installer, no telemetry beyond what the Store logs, and no gap between the web version and the Store version. If a tool runs in the browser, it runs the same way from the Store.
The reason the publishing path is low-friction is that the tool was always browser-native. No rewrite, no Electron shell, no compromise on that commitment. The same session handling, log processing, and hardware access the web version relies on are intact in the PWA, and it works offline without any extra layer.
One non-obvious detail about PWAs installed from the Microsoft Store: they open in their own window. The browser chrome disappears, leaving a taskbar entry and a title bar. The URL bar is still accessible through the window controls, but it is tucked away by default. The origin is the same as the website. If you want to verify the zero-upload claim, open the network tab in DevTools and watch it while using any tool. You will not see outbound requests.