Windows desktop & Store

A finished web app can be packaged for Windows in two ways:

A Windows desktop installer built with Tauri, which people download and install directly.
A Microsoft Store package ready to submit to the Microsoft Store.

Both are built on a GitHub Actions windows-latest runner, not on your machine, and the finished file is shared to you through Google Drive with a download link and a QR code.

GitHub token (required)

Windows packaging reuses your GitHub token. For this feature the token needs the workflow and actions:write scopes so LoopCodeLab can start the build workflow and read its result. See GitHub token to connect it and set the scopes.

Microsoft Store account (optional)

Publishing to the Microsoft Store needs a Partner Center (Microsoft Store) developer account.

Registering as an individual developer is currently free. Microsoft waived the earlier $19 one-time registration fee in its new individual-developer onboarding flow (current as of July 2026). A company account still carries a one-time fee of about $99 USD. Confirm the current amounts on Microsoft’s developer account page before you register.

Once you have an account, LoopCodeLab needs a store identity to build a Store package. You add these as the Windows Store credential in Settings:

identityName: the identity name from your Partner Center app reservation.
publisher: your publisher value in CN=... form.
Publisher display name: the name shown to customers, which is separate from the product name.

Code signing (optional)

For installer sideloading you can add a signing certificate: a .pfx file encoded as base64, plus its password, saved as the Windows signing credential in Settings. Signing lets people install your .exe without the unknown-publisher warning.

The Microsoft Store re-signs Store uploads for free, so a Store submission needs no signing certificate of your own.